Skip to main content
Glama

Download video

download_video

Prepare a video as MP4 (H.264 + AAC, plays everywhere), MP3, or a looping GIF of up to 10 s, and return a download link. The link works for 15 minutes after the last request. Long videos may still be preparing when this returns: then call check_download with the job_id. Counts against the caller's daily limit (40 per IP).

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": "download_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoOptional: end of the part to keep, in seconds (after start).
urlYesLink to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).
itemNoWhich video of a multi-video post (1-based); see get_video_info.
startNoOptional: start of the part to keep, in seconds.
qualityNoResolution cap (the smaller side, so vertical videos count the same). "audio" gives an MP3; "gif" a looping GIF of a selection up to 10 s (set start and end).720

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo)."New value: +"Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick)."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing asynchronous behavior, link expiry (15 minutes after the last request), and a per-IP daily quota of 40, which are exactly the operational facts an agent needs before calling. It also clarifies that the tool produces a downloadable artifact even though readOnlyHint is false.

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?

Four dense sentences, each carrying new information, with the format choice front-loaded and constraints after. No filler, though the parenthetical "(H.264 + AAC, plays everywhere)" is slightly promotional rather than decision-relevant.

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 (download link, job_id for polling) and the limits that determine success or failure. Nothing critical for correct invocation is missing.

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 quality, start, end, and item are already fully documented, and the description mostly restates them. The only added nuance is that a GIF selection is capped at 10 s, which the schema also states for the gif enum value.

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?

Specific verb plus resource with concrete output formats (MP4 H.264+AAC, MP3, looping GIF) and the artifact returned (a download link). It implicitly separates itself from check_download by naming that tool as the follow-up for still-processing jobs.

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

Usage Guidelines4/5

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

Gives an explicit follow-up path ("call check_download with the job_id" when the long video is not ready), which is the main branching decision. It does not contrast against edit_video or explain when to prefer a different extraction approach, but it covers the primary routing case.

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.

Resources