Zoom Recordings No-Auth
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
| Name | Description |
|---|---|
| zoom_refresh_tokenB | Refresh the Zoom OAuth2 access token using the refresh token and client credentials for API access |
| zoom_list_recordingsB | List Zoom cloud recordings from a user's Zoom account with pagination support |
| zoom_get_recording_detailsC | Get detailed information about a specific Zoom meeting recording including recording files and metadata |
| zoom_get_meeting_transcriptC | Get transcript files and content from a specific Zoom meeting recording if available |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: list_recordings for listing, get_recording_details for metadata, get_meeting_transcript for transcripts, and refresh_token for authentication. The descriptions reinforce these distinct roles, making tool selection unambiguous.
All tool names follow a consistent snake_case pattern with a 'zoom_' prefix and descriptive verb_noun combinations (e.g., list_recordings, get_meeting_transcript). This predictability enhances readability and usability across the tool set.
With 4 tools, this server is well-scoped for managing Zoom recordings, covering essential operations like listing, retrieving details, accessing transcripts, and handling authentication. Each tool earns its place without bloat or thinness for the domain.
The tool set provides strong coverage for core Zoom recording workflows, including listing, metadata retrieval, and transcript access, with authentication support. A minor gap exists in lacking update or delete operations for recordings, but this is not critical for typical read-only use cases.