@mnicole-dev/calcom-mcp-server

list-bookings

Retrieve bookings from your Cal.com account with filters for status, start/end times, event type, and attendee email. Use pagination to control result volume.

Instructions

List all bookings with optional filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-bookings"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results
`cursor`	No	Pagination cursor
`status`	No	Filter by booking status
`beforeEnd`	No	ISO 8601 datetime — only bookings ending before this
`afterStart`	No	ISO 8601 datetime — only bookings starting after this
`eventTypeId`	No	Filter by event type ID
`attendeeEmail`	No	Filter by attendee email

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read-only listing operation, but does not mention pagination behavior, default limits, output shape, authentication requirements, or any other notable behavior.

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

Conciseness5/5

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

The description is a single, tightly worded sentence with no filler. It front-loads the core action and resource while hinting at the optional filter capability, making it very easy to scan.

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?

This tool has 7 parameters, no output schema, and no annotations, yet the description only says 'List all bookings with optional filters.' It does not communicate pagination semantics, use cases, ordering, or how results are returned, leaving a competent agent under-informed for correct invocation.

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 documents all 7 parameters with 100% coverage, so the description does not need to explain each one. The phrase 'optional filters' adds a small layer of semantics, but the schema is already doing the heavy lifting, which yields the baseline score of 3.

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 clearly states the verb 'List' and the resource 'bookings', and indicates that filtering is supported. It is distinct from the sibling get-booking, which implies a single booking retrieval, though it does not explicitly name the sibling.

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 this tool versus alternatives such as get-booking or list-schedules. Saying 'with optional filters' gives a weak hint about customization, but no context, exclusions, or alternative routing is provided.

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