Skip to main content
Glama

Suprsonic

by io.github.O-mega-Enterprise
OverviewDiscussionsAdmin

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 (every YouTube download) answers status processing with a job_id instead: call again with that job_id to get the file. 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.

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.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. 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"
-]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing link expiry (one hour), the metadata returned, the async job_id flow for long/YouTube downloads, and a cost model (3 credits video, 2 audio, charged only on success, job polling free). These are exactly the operational facts an agent cannot infer from structured fields.

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 outcome and tightly packed with scope, async behavior, alternative tool, and cost. Minor redundancy in 'return a temporary download link. Returns a download link that expires after one hour,' which restates the same idea before adding the expiry.

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?

No output schema and no annotations covering the return payload, yet the description names the returned fields, the expiry, the async intermediate response, the polling contract, and the billing rules. An agent has everything needed to call it correctly on the first attempt.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies the url-vs-job_id split (call again with job_id to collect an in-progress download) and ties the audio formats to the cheaper 2-credit tier. Quality/format enums themselves are left to the schema.

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 and resource (download video from any URL) plus the concrete return artifact (temporary download link with name, size, duration, quality, format, title, thumbnail). It explicitly distinguishes itself from the sibling video-info tool, which returns details without a file.

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 when-to-use ('Use to get a video, or only its audio, as a file') and when-not ('For its details without downloading use video-info'), naming the alternative sibling. It also explains the async path: downloads over ~90 seconds answer status=processing with a job_id, and you call again with that job_id.

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

All Suprsonic toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources