Skip to main content
Glama

search_music_on_youtube

Search YouTube for songs using natural language queries and optionally play the best match immediately.

Instructions

Searches YouTube for music or songs based on a natural language query. If play_first_result is true, it immediately starts playing the best match.

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": {
      "query": "<query>"
    },
    "name": "search_music_on_youtube"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
play_first_resultNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does carry real weight and it discloses the most important trait: a conditional side effect where playback begins automatically when play_first_result is true. It does not cover what happens on failure or no match, whether playback interrupts the current track/queue, or any auth or quota constraints, so the behavioral picture is partial.

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 short sentences with no filler, front-loading the core action and following with the only meaningful option. Every clause carries information an agent needs.

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

Completeness3/5

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

An output schema exists, so return values need not be described. However, for a tool whose primary parameter triggers audible playback, the description leaves open whether search results are still returned when play_first_result is false and how this interacts with the existing queue — gaps that annotations would otherwise have covered.

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 description coverage is 0%, so the description must supply parameter meaning — and it does for both: 'query' is characterized as a natural language query, and 'play_first_result' is explained as immediately playing the best match. It lacks detail on what "best match" means and what is returned when the flag is false, keeping it below a 5.

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?

States a specific verb and resource ("Searches YouTube for music or songs") plus the input modality (natural language query), which clearly separates it from the playback-only siblings such as play_search_result or play_songs. It stops short of naming which sibling to use instead when the agent already has a known track, so it is clear but not fully differentiated.

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: the description explains the effect of play_first_result=true ("immediately starts playing the best match") but never says when to choose this tool over play_songs, start_radio, or dj_play_for_me, nor when to set play_first_result to false. An agent can infer the search-then-play flow but gets no explicit routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.