Skip to main content
Glama

Calendly

by io.github.pipeworx-io
OverviewAdmin

List Scheduled Events

list_scheduled_events
Read-onlyIdempotent

List scheduled meetings (events). Requires a user URI OR an organization URI (get them from current_user). Filter by status, time window, and paginate. Returns event URIs/UUIDs, names, start/end times, status, and locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoUser URI (from current_user). Provide user OR organization.
countNoNumber of results per page (default 20, max 100).
statusNoFilter by event status.
_apiKeyYesCalendly personal access token (sent as Bearer token)
page_tokenNoToken from a previous response for the next page.
organizationNoOrganization URI (from current_user). Provide user OR organization.
max_start_timeNoISO 8601 timestamp; only events starting at/before this time.
min_start_timeNoISO 8601 timestamp; only events starting at/after this time.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-calendly-api-key",
+    "user": "https://api.calendly.com/users/XXXXXXXXXXXXXXXX"
+  },
+  {
+    "_apiKey": "your-calendly-api-key",
+    "count": 50,
+    "max_start_time": "2024-12-31T23:59:59Z",
+    "min_start_time": "2024-01-01T00:00:00Z",
+    "organization": "https://api.calendly.com/organizations/XXXXXXXXXXXXXXXX",
+    "status": "active"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds valuable context beyond annotations: requires a user or organization URI (with reference to current_user) and lists filtering options. No contradiction.

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?

Two sentences, front-loaded with purpose and key constraints. Every sentence is necessary and no redundancy.

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?

The description covers required URIs, filtering, pagination, and return fields (compensating for missing output schema). Could mention pagination default/max or error conditions, but adequate given annotations.

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 coverage is 100%, so baseline is 3. The description mentions required parameters (user/organization) and filtering, but does not add significant new semantics beyond what the schema descriptions already provide.

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

Purpose5/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 resource 'scheduled events' (meetings). It distinguishes from siblings like 'get_event' (singular) and 'list_event_types' by specifying filtering, pagination, and return fields.

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 notes the prerequisite of obtaining a user or organization URI from 'current_user', implying a usage order. However, it does not explicitly state when to use this tool over alternatives like 'get_event' or 'list_invitees'.

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

All Calendly toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources