Skip to main content
Glama

zoom_get_recording_info

Extract metadata such as topic, duration, file size, and direct stream URL from public or password-protected Zoom cloud recording links using a URL and optional passcode.

Instructions

Extracts metadata (topic, duration, file size, direct stream URL) from a public or password-protected Zoom cloud recording link.

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_get_recording_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe Zoom cloud recording URL (e.g. https://zoom.us/rec/share/...)
passwordNoPasscode required to view or download the recording, if any.

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?

No annotations are supplied, so the description carries the full burden. It does add genuinely useful context that the link may be public or password-protected, and the 'direct stream URL' output implies no file is written. However, it is silent on failure behavior for a wrong passcode, on whether any network/permission prerequisites exist, and on rate limits or retry expectations for an external-service call.

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

Conciseness5/5

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

A single sentence that front-loads the verb and resource, then parenthetically lists the return fields. Every clause carries information; nothing is redundant or padded.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the metadata fields returned, which is the main thing an agent needs to know. What remains missing is error/edge-case behavior (invalid URL, wrong passcode, expired recording), which matters for a tool hitting an external service.

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 description coverage is 100%, so both parameters are already documented, which sets the baseline at 3. The description adds only marginal meaning by framing the link as possibly 'public or password-protected', which loosely explains why password is optional, but it offers no format, encoding, or validity guidance beyond the schema.

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

Purpose4/5

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

The description uses a specific verb ('Extracts metadata') against a specific resource ('Zoom cloud recording link') and enumerates the returned fields (topic, duration, file size, direct stream URL), so the agent knows exactly what it gets. It implicitly distinguishes itself from the download sibling by promising metadata rather than a file, but never names that sibling explicitly.

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 can infer 'use this to inspect a recording rather than download it', but there is no explicit when-to-use, when-not-to-use, or named alternative. With zoom_download_recording as a sibling, a routing sentence would have been cheap and valuable.

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