Skip to main content
Glama
surajpratap

Zoom MCP Server

by surajpratap

zoom_list_meetings

List Zoom meetings for a user with filters for scheduled, live, upcoming, or previous events.

Instructions

List meetings for a Zoom user. Can filter by type: scheduled, live, upcoming, or previous.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesZoom user ID or email address
typeNoMeeting type filter (default: scheduled)
page_sizeNoNumber of records per page (max 300)
next_page_tokenNoToken for next page of results
Behavior3/5

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

No annotations, so description carries burden; 'List' implies read-only, but lacks detail on rate limits, ordering, or default behavior of filter types.

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, no wasted words, front-loaded with purpose.

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?

Missing return value description (no output schema), no explanation of pagination despite page_size and next_page_token parameters.

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 has 100% coverage, description adds minimal value beyond 'Can filter by type'. Baseline 3 is appropriate.

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?

Clearly states 'List meetings for a Zoom user' with filter options, but doesn't differentiate from siblings like zoom_get_meeting or zoom_list_recordings.

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?

No guidance on when to use this tool versus alternatives (e.g., zoom_get_meeting for a single meeting). No mention of prerequisites or when not to use.

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/surajpratap/zoom-mcp-server'

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