Skip to main content
Glama

Get audio

get_audio
Read-onlyIdempotent

Read one audio file by media ID. Returns its stable link, source, brand, MIME type, size, duration, description, and Library status.

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": {
      "id": "<id>"
    },
    "name": "get_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMedia ID of the audio file, from list_audio or a generation output's id.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
idYesMedia ID of the file.
urlYesStable link to the file.
typeYesMedia family: image, video, or audio.
widthYesWidth in pixels, or null when not recorded.
heightYesHeight in pixels, or null when not recorded.
sourceYesuploaded, scraped (collected from a brand source), or generated.
file_sizeYesFile size in bytes.
mime_typeYesMIME type of the file.
created_atYesTime the file was stored.
in_libraryYesWhether the file is in its Brand Library.
descriptionYesText description of the file, or null when there is none.
duration_msYesDuration in milliseconds, or null when not recorded.
workspace_idYesWorkspace ID, or null for a personal workspace that has no ID.
generation_idYesID of the generation that produced the file, or null when none is recorded.
brand_session_idYesBrand session ID of the brand the file belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds only the shape of the payload (link, source, brand, MIME type, size, duration, description, Library status), and says nothing about error behavior for a missing or deleted ID or about auth/rate limits.

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?

Two compact sentences with the core action front-loaded and no filler. The second sentence enumerating returned fields is somewhat redundant given an output schema exists, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-record read tool, annotations cover side effects, the schema fully documents both parameters, and an output schema exists, so almost everything needed to invoke it correctly is present. The remaining gap is routing guidance versus list_audio and behavior on an unknown or deleted ID, and the return-field sentence duplicates the output schema instead of filling those gaps.

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%, with the id field already documented as a UUID sourced from list_audio or a generation output, and llm_model already explained as optional analytics metadata. The description adds nothing beyond 'by media ID', so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Read one audio file') and constrains it to a single record identified by media ID, which implicitly separates it from the bulk sibling list_audio. It does not explicitly name or contrast any sibling, so the differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance in the description; the only hint about provenance of the ID lives in the schema field text ('from list_audio or a generation output's id'), not in the description. An agent must infer that this is the single-record lookup counterpart to list_audio.

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