Skip to main content
Glama
meAmitPatil

Calendly MCP Server

by meAmitPatil

schedule_event

Schedule a meeting by creating an invitee for a specific Calendly event type and time, with support for additional guests, location, and UTM tracking.

Instructions

Schedule a meeting by creating an invitee for a specific event type and time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_typeYesURI of the event type to schedule
start_timeYesStart time for the event (ISO 8601 UTC format, e.g., 2025-10-02T18:30:00Z)
utm_mediumNoUTM tracking parameter for medium
utm_sourceNoUTM tracking parameter for source
event_guestsNoArray of additional email addresses to include (max 10)
invitee_nameNoFull name of the invitee (alternative to first_name/last_name)
utm_campaignNoUTM tracking parameter for campaign
invitee_emailYesEmail address of the invitee
invitee_phoneNoPhone number for SMS reminders (E.164 format, e.g., +14155551234)
location_kindNoType of meeting location (e.g., zoom_conference, google_conference, physical, ask_invitee)
invitee_timezoneYesTimezone of the invitee (e.g., America/New_York)
location_detailsNoLocation details (required for physical meetings or custom locations)
invitee_last_nameNoLast name of the invitee
invitee_first_nameNoFirst name of the invitee
questions_and_answersNoArray of question and answer pairs for booking form
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose side effects. It only says 'creating an invitee,' failing to mention email sending, calendar mutations, required permissions, or other behavioral details expected from a scheduling tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no filler, though 'creating an invitee' is slightly awkward. It efficiently communicates the main action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 15 parameters, no output schema, and no annotations, this minimal description leaves many operation details (e.g., guest limits, location handling, UTM parameters) unexplained. The agent gets little guidance beyond the schema, so completeness is low.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds only 'specific event type and time,' which does not meaningfully enhance understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('schedule') and resource ('meeting by creating an invitee'), clearly distinguishing it from siblings like cancel_event and list_events. The phrase 'creating an invitee' is slightly awkward but understandable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for scheduling meetings but provides no explicit comparison to alternatives or conditions for when to use this tool over others. It relies on the reader to infer context from the name and siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/meAmitPatil/calendly-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server