Skip to main content
Glama

Video Download

video-download
Read-only

Download video from any URL and return a temporary download link. Returns a download link that expires after one hour, with the file name, size, duration, quality, format, title and thumbnail. A download that takes longer than about a minute and a half (a long video from any site) answers status processing with a job_id instead: call again with that job_id to get the file. A finished download includes its job_id too. Use to get a video, or only its audio, as a file. For its details without downloading use video-info. Cost: video 3 credits, audio 2 credits, charged only when a call succeeds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "video-download"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL of the video or post containing a video. Send this, or job_id to collect a download in progress.
formatNoOutput format. An mp4 carries H.264 video and AAC audio whenever the site has the chosen quality in H.264 (most do); otherwise the codec the site has at that quality, such as VP9.mp4
job_idNoThe job_id of an answer whose status was processing: send it instead of url to get the file once it is ready. Checking is free; the call that returns the file is charged.
qualityNoDesired video quality (best available up to this resolution).720

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"Output format."New value: +"Output format. An mp4 carries H.264 video and AAC audio whenever the site has the chosen quality in H.264 (most do); otherwise the codec the site has at that quality, such as VP9."
  2. Changed3 schema fields changed
    • addedInput schema / properties / job_id
      Added value: +{
      +  "description": "The job_id of an answer whose status was processing: send it instead of url to get the file once it is ready. Checking is free; the call that returns the file is charged.",
      +  "type": "string"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"URL of the video or post containing a video."New value: +"URL of the video or post containing a video. Send this, or job_id to collect a download in progress."
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations by disclosing link expiry (one hour), the async job_id contract and that re-checking is free while the collecting call is charged, and a per-format credit cost (3 video / 2 audio) billed only on success. The annotations only declare read-only/open-world/non-destructive, so this pricing and lifecycle detail is genuinely additive context an agent needs before spending credits.

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?

Front-loaded with the core action and outcome, then layered with expiry, async handling, alternatives and cost in a logical order. It is dense but nearly every clause carries usable information; the enumeration of return fields is long but justified because no output schema exists.

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

Completeness5/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 supplies the return shape (link, file name, size, duration, quality, format, title, thumbnail) plus the alternate async return. Combined with cost, expiry and the retry contract, an agent has everything needed to invoke and interpret results for a four-parameter, open-world tool.

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 documented meaning for url, format, job_id and quality is already present and the baseline is 3. The description adds modest value by tying format to audio-only downloads and attaching credit costs per modality, but it does not explain enum behavior such as "best" or the relationship between quality and format beyond what the schema already says.

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 concrete verb and resource ("Download video from any URL and return a temporary download link") and immediately scopes the deliverable (file, or audio-only). It also names the sibling it is not — "For its details without downloading use video-info" — so the agent can separate it from video-info without inspecting schemas.

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

Usage Guidelines5/5

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

Gives explicit selection criteria: use this to obtain a file, use video-info for metadata only, and use the job_id path when a prior call answered status=processing. The condition that triggers the alternative flow ("a download that takes longer than about a minute and a half") is spelled out rather than left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.