Skip to main content
Glama

List music tracks

music_tracks_list
Read-onlyIdempotent

[read-only] List the brand’s uploaded music with audio URLs, source, license, attribution, duration, mood/tags and ad-use guidance. A bound key only accesses its brand; brandId can select a brand for an account-wide key. includeArchived also returns archived tracks. (Wraps GET /api/v2/music/tracks.)

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": "music_tracks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand id or personal. Omit to use the key’s bound brand, otherwise the owner’s active brand.
includeArchivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that with key-scope authorization behavior and archived-record behavior, but says nothing about ordering, limits, or payload size for what could be a long media listing. Useful additions against an already-covered safety bar land at 3.

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 scoping and authorization rules are front-loaded in the first sentence and the parenthetical endpoint note is tucked at the end where it does least harm. The return-field enumeration is dense but each item is decision-relevant; only the "(Wraps GET /api/v2/music/tracks.)" line is borderline filler.

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?

With no output schema, the description correctly takes on the job of describing returned fields, and it covers the two-parameter surface fully. The remaining gap is listing mechanics — pagination, default/max page size, sort order — which matters for a potentially large music library.

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 only 50% — brandId is documented while includeArchived has just a default and no description. The description compensates well: it explains the fallback chain for brandId (omit → key's bound brand → owner's active brand) and clarifies that includeArchived adds archived tracks to the result rather than filtering to them.

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 description uses a precise verb+resource ("List the brand's uploaded music") and goes further to enumerate what each record carries (audio URLs, source, license, attribution, duration, mood/tags, ad-use guidance). An agent can immediately distinguish this read/list tool from music_tracks_create without inspecting either 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?

It gives clear context for when the brand-scoped path applies versus the account-wide path ("A bound key only accesses its brand; brandId can select a brand for an account-wide key"), which is exactly the decision an agent faces. It stops short of explicitly naming an alternative or a when-not-to-use condition, so it is not a full 5.

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