Skip to main content
Glama

Fetch Audio Download

fetch_audio_download
Read-onlyIdempotent

Fetch a completed project's audio as inline MCP audio content 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.

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_audio_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.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description adds real substance on top: the 8 MiB inline cap, the fallback behavior of returning an original-file download link on overflow, and the host/HTTPS constraint. That is exactly the operational context an agent cannot get from the annotation flags.

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?

Four short sentences, front-loaded with the core action and delivery format, then prerequisites, then the size-limit behavior. No sentence is filler and nothing important is buried.

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 definition covers what is returned in both the success case (inline audio) and the overflow case (download link), plus client compatibility and host requirements. An agent has everything needed to invoke it correctly.

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% and both parameters are already documented there, including the 8388608-byte cap and the requirement to preserve query parameters. The description restates the same facts rather than adding new meaning, so the baseline of 3 applies.

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 ('Fetch a completed project's audio') plus the delivery form ('inline MCP audio content'), which separates it from fetch_image_download and fetch_video_download without opening any schema.

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 clear preconditions: the project must be completed, the URL must be the exact signed URL with query parameters, and HTTPS on the configured media host is required. It stops short of naming an alternative path (e.g., using get_audio_project for non-completed projects), so there is no explicit when-not guidance.

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.