Skip to main content
Glama
Sign In
youtube-music

youtube-music

by VirtualyMichael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_result

Plays a selected song, video, or playlist from your last YouTube Music search by specifying its kind and result number.

Instructions

Press play on a result from the latest search_music (use its kind and number).

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": {
      "kind": "<kind>",
      "number": "<number>"
    },
    "name": "play_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It reveals only that the call is stateful (dependent on the latest search results); it says nothing about what playback does to the current queue, whether it requires an active session/account, or what happens on an invalid kind or stale search. This is a significant gap for a mutation-like playback action.

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?

A single sentence with no waste; the action and its dependency on search_music are both front-loaded. Every clause earns its place.

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?

For a two-parameter play tool with no annotations and no output schema, the description adequately explains the calling context (must follow search_music) but omits parameter value ranges, failure behavior, and playback side effects. Minimum viable, with clear gaps.

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 coverage is 0%, so the description must compensate, and it does partially by telling the agent both parameters come from the latest search_music result (kind and number). However, it never defines what 'kind' values exist or how 'number' indexes results, leaving the meaning of both parameters under-specified.

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 (press play) and resource (a result from the latest search_music), and explicitly ties itself to the search_music result set, which distinguishes it from play_music and play_playlist. An agent can tell what it does without opening the 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?

The description gives a clear precondition: it operates on a result from the latest search_music, implying it should be called after a search. It does not name when-not to use it or contrast explicitly with play_music/play_playlist, so the routing guidance is implicit rather than complete.

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

Deploy Server

Other Tools