Skip to main content
Glama

Download a track

download_track

Get a download link for the final file. This spends Tuney credits (mp3, wav, or a zip of stems).

    Returns download_url right away when the file is cached, otherwise a task_id to pass to
    wait_for_task with kind="download". Links expire, so share them promptly. download_url is on
    the Tuney API host; download_direct_url is the same file in Cloud Storage.
    For format="stems" the link is a zip with one mp3 per part; the result's `contents` map
    gives the readable name of each file (melody, chords, bass, drums, swoosh fx, impact fx).
    To show stems to the user: fetch the zip, unzip it, rename the files with that map and
    attach them. Never download the same track twice.
    

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": {
      "cue_id": "<cue_id>"
    },
    "name": "download_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
cue_idYes
formatNomp3

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only tell the agent this is a non-idempotent, non-read-only, non-destructive operation; the description adds the material facts: it spends Tuney credits, returns synchronously from cache or asynchronously as a task_id, links expire, and there are two distinct URL hosts. It also discloses the stems-specific payload shape and the contents map needed to label files.

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?

The most important fact, that this spends credits, is front-loaded in the first line, and each following clause adds operational value (routing to wait_for_task, expiry, host distinction, stems handling). It is dense but earns most of its length; the stems display workflow is slightly verbose relative to its frequency.

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?

An output schema exists, yet the description still supplies the one thing the schema cannot: the branching contract of download_url versus task_id and the routing that follows each. Combined with the credit-cost warning and stems handling instructions, an agent has everything required to invoke and follow up correctly.

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 0%, so the description must carry the parameter burden, and it substantially does for format: the enum values mp3/wav/stems are explained, and format="stems" is spelled out as a zip with one mp3 per part, plus the readable part names returned in the contents map. cue_id is left unexplained, though its role is inferable from the download context.

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?

The opening sentence names a specific verb and resource: obtain a download link for the final rendered file, and notes the credit cost and the three formats. That is clearly distinguishable from metadata siblings like get_track or find_tracks, which do not produce a link or spend credits.

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?

It gives concrete operating guidance: pass the returned task_id to wait_for_task with kind="download", share links promptly because they expire, and never download the same track twice. What it lacks is an explicit statement of when to prefer this over get_track (metadata only) or when a fresh download is warranted versus reusing a prior one.

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.