Skip to main content
Glama

zoom_download_recording

Downloads Zoom cloud recording MP4s directly to local disk using Unified Player session tokens without browser automation; accepts recording URL, optional passcode, and output path.

Instructions

Downloads a Zoom cloud recording directly to local disk using reverse-engineered Unified Player session tokens without browser automation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "zoom_download_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe Zoom cloud recording URL
passwordNoPasscode required to view or download the recording, if any.
output_pathNoDestination file path or directory. Defaults to ./downloads/<topic>.mp4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does add real signal: download works via reverse-engineered Unified Player session tokens and requires no browser automation, implying URL-plus-passcode is the auth path. It omits practical behavior such as retry/failure modes, whether an existing file at output_path is overwritten, speed or rate limits on large recordings, and what is returned on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the key differentiation (direct download, no browser) comes first. The phrase about reverse-engineered session tokens is slightly implementation-flavored but still earns its place as behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter write-to-disk tool with no annotations and no output schema, the definition covers what the tool does and the auth mechanism but leaves gaps an agent would care about: return value or confirmation path, overwrite/error semantics, and any dependency on the recording being accessible. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each of the three parameters is already documented, including the ./downloads/<topic>.mp4 default. The description adds no further meaning about how url, password, or output_path interact (for example whether password is mandatory for passcode-protected links), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Downloads') and resource ('a Zoom cloud recording') plus the destination ('directly to local disk'), which cleanly separates it from the sibling zoom_get_recording_info, which only reads metadata. An agent can pick the right tool from this sentence alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it actually wants the file on disk rather than just details. There is no explicit 'use this when / not when', no mention of whether zoom_get_recording_info should be called first to obtain the URL, and no note on preconditions such as cloud-recording being enabled or the recording still being available.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools