Skip to main content
Glama

Find music

find_music
Read-only

Search the studio's music shelf (beds made with Google Lyria, and uploads with their licence) by words, mood, genre, tempo and length. With video_seconds, tracks that cover the whole video come first, closest length first. Each track says whether it needs a credit and gives the exact credit. Pass track_id as audio.track_id to render_video.

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

Input Schema

NameRequiredDescriptionDefault
moodNo
genreNo
limitNo
queryNoWords in the title, mood, genre or prompt
tempoNo
credit_freeNoLeave out tracks that need a credit in the post
max_secondsNo
min_secondsNo
video_secondsNoOutput video length: tracks that cover it, closest length first

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 only declare readOnlyHint=true, and the description adds real behavioral detail beyond that: the result ordering rule for video coverage, that tracks are licence-tagged, and that each result reports whether a credit is needed plus the exact credit text. It does not describe what happens with limit/credit_free or how an empty shelf is reported.

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?

Four short sentences, each carrying distinct information: what is searched, how ranking works, what metadata comes back, and how to chain into render_video. The parenthetical about Lyria beds and licence uploads earns its place by explaining the credit behavior that follows later.

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 9-parameter, optional-only search tool with no output schema, the description covers the important pieces: ranking, credit metadata, and cross-tool chaining. Missing only secondary details such as limit behavior and empty-result handling, which keeps it just short of fully complete.

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 33%, and the description compensates well by mapping the searchable facets (words, mood, genre, tempo, min/max length) and explaining the ranking semantics of video_seconds. It adds no meaning for limit or credit_free, which remain documented only by the schema's brief default text.

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?

Names a specific verb and resource ("Search the studio's music shelf") and enumerates the facets it searches: words, mood, genre, tempo and length. It also implicitly separates itself from make_music by framing the tool as retrieval from an existing shelf, and it names the downstream consumer (render_video) explicitly.

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?

Gives a clear condition for the key parameter ("With video_seconds, tracks that cover the whole video come first") and tells the agent exactly what to do with results ("Pass track_id as audio.track_id to render_video"). It stops short of stating when to choose a different tool, e.g. when to use make_music instead of searching.

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