Zoom 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_meetingC | Create a meeting |
| list_meetingsB | List scheduled meetings |
| delete_a_meetingB | Delete a meeting with a given ID |
| get_a_meeting_detailsA | Retrieve the meeting's details with a given ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_meetings | A prompt to list meetings |
| create_meeting | A prompt to create a meeting |
| delete_a_meeting | A prompt to delete a meeting |
| get_a_meeting_details | A prompt to get a meeting's details |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation on meetings: create, delete, get details, and list. There is no overlap in functionality, making it easy for an agent to select the correct tool.
Most tools follow a verb_noun pattern (e.g., create_meeting, list_meetings), but two include the article 'a' (delete_a_meeting, get_a_meeting_details) which is a minor inconsistency.
With 4 tools, the server is well-scoped for meeting management. The number is appropriate for the domain and avoids redundancy.
The tool surface covers create, read, delete, and list operations but lacks an update meeting tool. This is a notable gap for full CRUD coverage in meeting management.