Skip to main content
Glama

List music tracks

list_music_tracks
Read-only

List the background music library (music.trackName for render_video) with moods, descriptions and lengths. Use it only when the user asks for a library track: you cannot listen to them, so music.generateMusic: true is the better default.

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_music_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoA mood, e.g. calm, energetic. The response lists them.
searchNoWords to find in the name or description, e.g. piano.
instrumentalNotrue for instrumental tracks only, false for tracks with words.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
methodYes
statusYes
endpointYes
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the agent cannot audition the tracks, and the returned names plug into `render_video`'s `music.trackName`. It stops short of describing result volume, pagination, or whether the library is curated vs. user-supplied.

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?

Two sentences, both load-bearing. The resource and return contents come first, then the usage constraint and alternative, so the most decision-relevant information is front-loaded with no 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 an output schema present, return values need no explanation, and all three optional parameters are documented. Purpose, limitation, and the routing alternative are all covered; only edge context (empty results, whether filters combine, library scope) is absent, which is minor for a read-only list tool.

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%, so all three filters (mood, search, instrumental) are already documented, and the description adds no syntax, matching rules, or combination behavior beyond them. The only extra hint — that the response lists available moods — duplicates what the schema already says for the `mood` property.

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 ('List the background music library') and immediately names what the results carry: moods, descriptions, lengths. It also ties the output to a concrete downstream field (`music.trackName` for `render_video`), so an agent knows exactly what this tool returns and where it is consumed.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ('Use it only when the user asks for a library track') and names the preferred alternative for the common case (`music.generateMusic: true`), with the reason ('you cannot listen to them'). This is the when/when-not/alternative pattern at full strength.

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