Skip to main content
Glama
thenavidm

Calendly MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Recaps

list_recaps
Read-onlyIdempotent

Retrieve Calendly meeting recaps and filter by event, attendee, status, or date range to locate specific meeting summaries.

Instructions

List Recaps. Reads Calendly data. Supports bounded opaque page_token retrieval. Required scopes: meeting_recaps:read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoThe number of rows to return
eventNoFilter results to recaps associated with a specific event scheduled via Calendly. This field corresponds to the `/scheduled_events` endpoint.
statusNoFilter by recap availability. When omitted, returns **Available** recaps only. - `available` — completed recaps with summary content - `processing` — recaps still being generated - `unavailable` — recaps that cannot be retrieved
accountNoNamed private Calendly account; selects credentials, not an organization URI.
attendeeNoFilter results to recaps that include a specific attendee email address.
end_timeNoReturn recaps for meetings that start before (or start at) this time (ISO 8601).
all_pagesNoRead bounded opaque page_token pages; each request consumes quota. Not a snapshot or guaranteed complete backup.
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
start_timeNoReturn recaps for meetings that end after (or end at) this time (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely new context: the required OAuth scope (meeting_recaps:read) and the fact that retrieval is bounded-opaque-pagination based, which an agent needs for auth planning.

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 terse sentences, front-loaded with the operation and then the two added facts. Nothing is padded, though the fragments read more like generated scaffolding than a tight human sentence.

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

Completeness4/5

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

For a safe read-only list tool with a rich 10-param schema and full annotations, the description covers the missing pieces (scope requirement, pagination nature). The default-status-filter behavior and return shape live in the schema, which is acceptable given no output schema requirement.

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 all ten parameters are already fully documented in the schema (including the status default and page_token semantics). The description adds no parameter-level detail, so the baseline 3 applies.

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

Purpose3/5

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

The description states a verb+resource ("List Recaps") and adds that it reads Calendly data, so the basic purpose is clear. However, it does nothing to distinguish it from the adjacent get_recap, update_recap, and delete_recap siblings, and "Reads Calendly data" is filler rather than differentiation.

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 guidance on when to use list_recaps versus get_recap or the other recap tools, and no described conditions or prerequisites. The only usable signal is the implied read-vs-mutate split from the name.

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