Zoom API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 54 tools
Every tool has a clearly distinct purpose based on resource type and action. Tools are organized by resource (meeting, user, webinar, channel, etc.) and operation (create, get, list, update, delete), with no ambiguous overlaps. The consistent pattern makes it easy to distinguish between tools like get_meeting, list_meetings, and delete_meeting.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. Verbs (create, get, list, update, delete, send, search) are used predictably, and nouns clearly identify the resource type. There are no deviations in naming conventions across the entire set.
With 54 tools, this is an extremely large set that feels heavy and overwhelming for a single server. While Zoom's API is comprehensive, this many tools suggests poor scoping or a direct mapping of API endpoints without consolidation, making it difficult for agents to navigate efficiently.
The tool set provides comprehensive CRUD/lifecycle coverage across all major Zoom resources (meetings, webinars, users, channels, webhooks, recordings, etc.). It includes create, get, list, update, and delete operations consistently, plus specialized actions like sending messages and generating reports, leaving no obvious gaps for the domain.