Skip to main content
Glama

Fetch Video Download

fetch_video_download
Read-onlyIdempotent

Fetch a completed project's video as an embedded MCP binary resource for compatible clients. Use the exact signed download URL, including query parameters. Requires HTTPS at the configured Magic Hour media host. Read-only; inline content is limited to 8 MiB, or a smaller requested max_bytes. Returns the original-file download link when the media exceeds this limit. For playback or downloads in ChatGPT, open Magic Hour’s result card with get_video_project or wait_for_video_project using the existing project ID. When this tool shows a result card in ChatGPT, use its Download control. Do not put the signed URL in a chat 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": {
      "download_url": "<download_url>"
    },
    "name": "fetch_video_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_bytesNoPositive maximum inline download bytes, capped at 8388608 bytes (8 MiB). Larger files return an original-file download link.
download_urlYesExact HTTPS URL from a completed project’s downloads or exact_download_urls. Preserve all query parameters; must use the configured Magic Hour media host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / max_bytes / description
      Previous value: -"Positive maximum raw download bytes. The server caps this at 8388608 bytes (8 MiB); use the original URL directly for larger files."New value: +"Positive maximum inline download bytes, capped at 8388608 bytes (8 MiB). Larger files return an original-file download link."
  2. Changed2 schema fields changed
    • addedInput schema / properties / download_url / description
      Added value: +"Exact HTTPS URL from a completed project’s downloads or exact_download_urls. Preserve all query parameters; must use the configured Magic Hour media host."
    • addedInput schema / properties / max_bytes / description
      Added value: +"Positive maximum raw download bytes. The server caps this at 8388608 bytes (8 MiB); use the original URL directly for larger files."
  3. Changed1 schema field changed
    • changedInput schema / properties / max_bytes / default
      Previous value: -15728640New value: +8388608
  4. Changed1 schema field changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
      -  "type": "string"
      -}
  5. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: HTTPS and configured media-host requirement, an 8 MiB inline cap overridable by max_bytes, fallback to an original-file download link above the cap, and ChatGPT result-card handling. Those are operational constraints an agent cannot infer from the annotations.

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 what the tool does, then limits, then alternatives. It is slightly long and the ChatGPT result-card sentences partly repeat each other, but no sentence is wasted on filler.

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?

For a two-parameter read tool with no output schema, the description covers purpose, byte-limit behavior, host requirement, client-specific handling, and sibling alternatives. An agent has everything needed to call it correctly and to route elsewhere when appropriate.

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% and both parameters are already described there, including the max_bytes cap and the instruction to preserve query parameters. The description largely restates the host requirement and byte limit, adding only security context around the signed URL, so baseline 3 is appropriate.

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 (Fetch) and resource (a completed project's video) plus the delivery mechanism (embedded MCP binary resource for compatible clients), which separates it from sibling download tools for audio and image as well as from project-metadata tools like get_video_project.

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 routing: use this tool with the exact signed URL, but for playback or downloads in ChatGPT open the result card via get_video_project or wait_for_video_project. It also states a negative rule (do not put the signed URL in a chat link), so an agent knows both when to use it and when not to.

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.