Skip to main content
Glama

List audio files

list_audio
Read-onlyIdempotent

List audio files across your brands, newest first: generated outputs and files added to a Brand Library. Returns each file's media ID, stable link, source, MIME type, size, duration, and Library status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of matching items to include on this page. Omit to return 20 items.
cursorNoPass next_cursor from the previous result to get the next page.
sourceNoFilter by how the file was obtained: uploaded for uploaded files, scraped for files collected from brand sources, or generated for model outputs.
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.
in_libraryNoOnly files in (true) or not in (false) the Library.
brand_session_idNoBrand whose audio files to retrieve. Use its Brand session ID from list_brands; omit to leave results unfiltered by brand.

Output Schema

NameRequiredDescriptionDefault
itemsYesMatching files, newest first.
has_moreYesWhether more results follow this page.
next_cursorYesPass as cursor to get the next page. Null when no more results follow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, idempotentHint, openWorldHint=false), so the bar is lower, and the description still adds real behavior: results are ordered newest first and span both generated outputs and Brand Library files. What it does not add is pagination behavior or result-size limits beyond the schema, so it falls short of a 5.

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 scope front-loaded and no filler. Minor redundancy in enumerating return fields that the output schema already documents, but nothing is confusing or padded.

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 read-only, zero-required-parameter listing tool with full schema coverage and an output schema, the definition supplies enough: scope, ordering, content origins, and return shape. The remaining gap is that pagination/next-page behavior and sibling routing are left entirely to the schema and surrounding catalog.

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%, including the source enum and the brand_session_id sourcing hint, so the schema does the heavy lifting and a 3 is the baseline. The description contributes only indirect signals ('across your brands' for brand filtering, 'Library status' for in_library) and says nothing about limit/cursor paging or the source filter.

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 gives a specific verb and resource ('List audio files'), plus scope ('across your brands'), ordering ('newest first'), and the two content origins ('generated outputs and files added to a Brand Library'). It clearly delimits itself as an audio-only lister, though it never names a sibling (e.g., get_audio for a single file, list_library) to sharpen the distinction.

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

Usage Guidelines3/5

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

Usage is only implied by the resource name — an agent can infer 'use this to enumerate audio' but the definition never states when to prefer it over get_audio, view_files, or list_library, nor does it set exclusions. No prerequisites or call-order guidance (e.g., 'get brand_session_id from list_brands first') appear, despite a brand-scoped parameter existing.

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