Zoom Phone + Virtual Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOOM_CLIENT_ID | Yes | Your Zoom Client ID from Server-to-Server OAuth app | |
| ZOOM_ACCOUNT_ID | Yes | Your Zoom Account ID from Server-to-Server OAuth app | |
| ZOOM_CLIENT_SECRET | Yes | Your Zoom Client Secret from Server-to-Server OAuth app |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| phone_get_account_call_historyC | Get the Zoom Phone account's call history for a date range. Scope: phone:read:call_history:admin. |
| phone_get_account_call_logsA | Get the Zoom Phone account's call logs for a date range (legacy-style logs, complements call_history). Scope: phone:read:call_log:admin. |
| phone_get_call_log_detailsB | Get details for a single call log by ID. |
| phone_get_call_elementC | Get a single call element (a leg/segment of a call, e.g. hold, transfer, recording marker) by ID. |
| phone_get_user_call_historyC | Get a specific Zoom Phone user's call history for a date range. Scope: phone:read:call_history. |
| phone_get_user_call_logsB | Get a specific Zoom Phone user's call logs for a date range. |
| phone_get_user_call_handling_settingsA | Get call handling settings (business hours / closed hours / holiday routing) for a Zoom Phone user. Scope: phone:read:call_handling_setting or phone:read:call_handling_setting:admin. |
| phone_update_user_call_handling_settingB | Update a user's call handling setting for a specific hour type (business_hours, closed_hours, or holiday_hours). WRITE OPERATION — modifies live call routing configuration. |
| phone_get_auto_receptionist_call_handling_settingsC | Get call handling settings for an auto receptionist (IVR). |
| phone_update_auto_receptionist_call_handling_settingC | Update an auto receptionist's call handling setting for a specific hour type. WRITE OPERATION — modifies live call routing configuration. |
| va_get_articlesC | List knowledge base articles for a Zoom Virtual Agent knowledge base. |
| va_get_articleC | Get a single knowledge base article by ID. |
| va_create_articleB | Create a new knowledge base article. WRITE OPERATION — adds content the bot can answer from. |
| va_update_articleC | Update an existing knowledge base article. WRITE OPERATION. |
| va_sync_knowledge_baseB | Kick off an external knowledge-base sync job for a Zoom Virtual Agent KB. WRITE OPERATION — starts an async sync. |
| va_get_sync_statusB | Check the status of a previously started knowledge-base sync job. |
| va_get_engagementsB | Get Zoom Virtual Agent engagement report data (bot conversation sessions) for a date range. |
| va_get_query_detailsB | Get Zoom Virtual Agent query-level detail (what users asked, whether it was answered) for a date range. |
| va_get_transcriptsC | Get Zoom Virtual Agent conversation transcripts for a date range. |
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 19 tools
Most tools are clearly distinct: phone_ tools handle call data/routing while va_ tools handle virtual agent content and analytics. There's some potential confusion between phone_get_account_call_history and phone_get_account_call_logs (similar purpose, distinguished by legacy-style), and between phone_get_call_log_details and phone_get_call_element (both detail views of call segments, but one is by log ID vs element ID).
Names follow a consistent prefix_verb_noun pattern: phone_/va_ prefixes cleanly separate domains, and verbs like get/update/create are used consistently. The single deviation is va_sync_knowledge_base, which uses 'sync' as a verb rather than the otherwise consistent get/create/update pattern, making it slightly inconsistent with the established naming style.
19 tools is at the upper edge of the reasonable range, but it spans two distinct product domains (Zoom Phone and Virtual Agent) with rich feature sets. Each tool covers a meaningful operation. Slightly heavy because it combines two domains, but each tool earns its place within its domain.
The Virtual Agent side is well-covered with articles CRUD (create/get/update but missing delete), sync operations, and analytics queries. The phone side covers call history, logs, and call handling settings with read/update but lacks create operations (which makes sense for read-centric call data). Minor gaps: no delete article, and the call-handling settings lack full lifecycle coverage, but the core workflows are complete.