zoom-dl
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zoom_get_recording_infoA | Extracts metadata (topic, duration, file size, direct stream URL) from a public or password-protected Zoom cloud recording link. |
| zoom_download_recordingA | Downloads a Zoom cloud recording directly to local disk using reverse-engineered Unified Player session tokens without browser automation. |
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 2 tools
The two tools target clearly different operations: metadata extraction versus actual file download. An agent can unambiguously choose between inspecting a recording link and downloading it, and the download tool even implies it may rely on info retrieved first.
Both names follow a strict `zoom_<verb>_<noun>` snake_case pattern with a consistent `zoom_` prefix. There is no mixing of conventions or vague verbs.
Two tools is thin even for a narrow single-purpose server, though both clearly earn their place. The surface feels minimal rather than over- or under-scoped for the stated task.
For the stated purpose of pulling a Zoom cloud recording from a link, the metadata-inspect and download pair covers the core workflow. Minor gaps exist, such as enumerating recordings within a meeting or selecting quality/format before download.