Skip to main content
Glama
thenavidm

Calendly MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Contacts

list_contacts
Read-onlyIdempotent

Retrieve and filter Calendly contacts by name, email, company, and location, then sort and page through records for syncing or reviewing contact data.

Instructions

List Contacts. Reads Calendly data. Supports bounded opaque page_token retrieval. Required scopes: contacts:read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoFilter results by partial match on city(ies). Accepts a comma-separated list-- each segment is matched independently (commas in the query string separate values).
nameNoFilter results by partial match on name(s). Accepts a comma-separated list-- each segment is matched independently (commas in the query string separate values).
sortNoOrder results by the specified field and direction. Accepts comma-separated list of {field}:{direction} values. Supported fields are: created_at, updated_at. Sort direction is specified as: asc, desc.
countNoThe number of rows to return
emailNoFilter results by exact match on email address. Accepts a comma-separated list.
stateNoFilter results by exact match on state(s), province(s), or region(s). Accepts a comma-separated list of values.
accountNoNamed private Calendly account; selects credentials, not an organization URI.
companyNoFilter results by partial match on company name(s). Accepts a comma-separated list-- each segment is matched independently (commas in the query string separate values).
countryNoFilter results by exact match on two-letter country code (ISO 3166-1 alpha-2). Accepts a comma-separated list.
excludeNoOmit the listed fields from the response. Currently only `custom_fields` is supported. When omitted, all fields are returned.
timezoneNoFilter results by exact match on the IANA time zone name(s). Accepts a comma-separated list of time zones.
all_pagesNoRead bounded opaque page_token pages; each request consumes quota. Not a snapshot or guaranteed complete backup.
job_titleNoFilter results by partial match on job title(s). Accepts a comma-separated list-- each segment is matched independently (commas in the query string separate values).
max_itemsNoMaximum returned records with all_pages=true, default 1000. At most 100 requests; output includes continuation state.
page_tokenNoThe token to pass to get the next or previous portion of the collection
phone_numberNoFilter results by exact match on phone number. Accepts a comma-separated list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the bar is lower. The description adds real value beyond them: the required scope ('contacts:read') tells the agent about auth requirements, and the 'bounded opaque page_token retrieval' phrasing signals quota-consuming pagination rather than an exhaustive snapshot.

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?

Three short sentences, front-loaded with the action, no padding. 'Reads Calendly data' is mild filler given the name already implies it, keeping it just short of a 5.

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

Completeness3/5

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

With 16 optional filter/pagination parameters and no output schema, the description is thin on how the filters combine or what the pagination/continuation state looks like, though the 100% schema coverage compensates substantially. Adequate but not complete for a tool of this complexity.

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?

Schema description coverage is 100%, so the schema already documents all 16 parameters in detail (filters, sort syntax, count bounds, all_pages/max_items interplay). The description adds only a generic note about bounded page_token retrieval, which is baseline 3 territory.

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 states a clear verb+resource ('List Contacts') and identifies the domain ('Reads Calendly data'). It does not explicitly differentiate itself from siblings like get_contact or list_contact_custom_field_definitions, but the naming convention makes the list-vs-get distinction inferable.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives such as get_contact (single record) or list_contact_custom_field_definitions. The mention of page_token retrieval implies a large-collection use case but never says so explicitly or names an alternative.

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

Deploy Server

Other Tools