Read connected scheduling profiles, event types, available meeting times, busy times, meetings and invitees. Account authorization is required. Booking, cancellation, deletion and webhook changes are not enabled.
What you can do (9)
What you can do
Available commands: 9 (9 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Read the connected Calendly user — calendly.users.me |
Read |
List a user's event types — calendly.event-types.list |
Read |
Read an event type — calendly.event-types.get |
Read |
Read available meeting times — calendly.event-types.available-times |
Read |
List scheduled meetings — calendly.events.list |
Read |
Read a scheduled meeting — calendly.events.get |
Read |
List a meeting's invitees — calendly.invitees.list |
Read |
Read a meeting invitee — calendly.invitees.get |
Read |
Read a user's busy times — calendly.busy-times.list |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Calendly, then enter the issued values in the connection form below.
- For your account, create a Personal Access Token under Calendly Integrations & apps → API and webhooks and enter Access token. For OAuth, register a developer application with the exact redirect URI, enter Client ID/Secret, save and authorize. Your plan and scopes limit scheduling access.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| OAuth callback URL (optional) | Optional |
| Access token | Optional |
| OAuth client ID | Optional |
| OAuth client secret | Optional |
| Return URL after authorization | Optional |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Read the connected Calendly user — calendly.users.me
Run Read the connected Calendly user with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 15 seconds.
List a user's event types — calendly.event-types.list
Run List a user's event types with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
user |
string | Required | Connected user URI | minLength: 1; maxLength: 200; pattern: "^https://api\\.calendly\\.com/users/[A-Za-z0-9_-]{1,128}$" |
count |
integer | Optional | Results per page | minimum: 1; maximum: 20 |
pageToken |
string | Optional | Page token | minLength: 1; maxLength: 4096 |
active |
boolean | Optional | Active event types only |
Full JSON Schema
Example input
{
"user": "https://api.calendly.com/users/user_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read an event type — calendly.event-types.get
Run Read an event type with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
eventTypeId |
string | Required | Event type ID | minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$" |
Full JSON Schema
Example input
{
"eventTypeId": "type_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read available meeting times — calendly.event-types.available-times
Run Read available meeting times with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
startTime |
string | Required | Availability start in UTC | minLength: 1; maxLength: 24; format: "date-time" |
endTime |
string | Required | Availability end in UTC | minLength: 1; maxLength: 24; format: "date-time" |
offset |
integer | Optional | Local result offset | minimum: 0; maximum: 10000 |
limit |
integer | Optional | Results per page | minimum: 1; maximum: 20 |
eventType |
string | Required | Event type URI | minLength: 1; maxLength: 200; pattern: "^https://api\\.calendly\\.com/event_types/[A-Za-z0-9_-]{1,128}$" |
Full JSON Schema
Example input
{
"startTime": "2099-01-01T00:00:00Z",
"endTime": "2099-01-02T00:00:00Z",
"eventType": "https://api.calendly.com/event_types/type_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
List scheduled meetings — calendly.events.list
Run List scheduled meetings with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
user |
string | Required | Connected user URI | minLength: 1; maxLength: 200; pattern: "^https://api\\.calendly\\.com/users/[A-Za-z0-9_-]{1,128}$" |
count |
integer | Optional | Results per page | minimum: 1; maximum: 20 |
pageToken |
string | Optional | Page token | minLength: 1; maxLength: 4096 |
status |
string | Optional | Meeting or invitee status | enum: ["active","canceled"]; minLength: 1; maxLength: 128 |
minStartTime |
string | Optional | Earliest meeting start in UTC | minLength: 1; maxLength: 24; format: "date-time" |
maxStartTime |
string | Optional | Latest meeting start in UTC | minLength: 1; maxLength: 24; format: "date-time" |
Full JSON Schema
Example input
{
"user": "https://api.calendly.com/users/user_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read a scheduled meeting — calendly.events.get
Run Read a scheduled meeting with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
eventId |
string | Required | Meeting ID | minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$" |
Full JSON Schema
Example input
{
"eventId": "event_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
List a meeting's invitees — calendly.invitees.list
Run List a meeting's invitees with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
eventId |
string | Required | Meeting ID | minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$" |
count |
integer | Optional | Results per page | minimum: 1; maximum: 20 |
pageToken |
string | Optional | Page token | minLength: 1; maxLength: 4096 |
status |
string | Optional | Meeting or invitee status | enum: ["active","canceled"]; minLength: 1; maxLength: 128 |
Full JSON Schema
Example input
{
"eventId": "event_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read a meeting invitee — calendly.invitees.get
Run Read a meeting invitee with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
eventId |
string | Required | Meeting ID | minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$" |
inviteeId |
string | Required | Invitee ID | minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$" |
Full JSON Schema
Example input
{
"eventId": "event_1",
"inviteeId": "invitee_1"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Read a user's busy times — calendly.busy-times.list
Run Read a user's busy times with Calendly. This is a read command; it does not grant access beyond the connected account's permissions.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
user |
string | Required | Connected user URI | minLength: 1; maxLength: 200; pattern: "^https://api\\.calendly\\.com/users/[A-Za-z0-9_-]{1,128}$" |
startTime |
string | Required | Availability start in UTC | minLength: 1; maxLength: 24; format: "date-time" |
endTime |
string | Required | Availability end in UTC | minLength: 1; maxLength: 24; format: "date-time" |
offset |
integer | Optional | Local result offset | minimum: 0; maximum: 10000 |
limit |
integer | Optional | Results per page | minimum: 1; maximum: 20 |
Full JSON Schema
Example input
{
"user": "https://api.calendly.com/users/user_1",
"startTime": "2099-01-01T00:00:00Z",
"endTime": "2099-01-02T00:00:00Z"
}
At most 1 provider requests per invocation; timeout: 15 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.