Skip to main content
Glama
Sign In
youtube-music

youtube-music

by VirtualyMichael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

music_control

Play, pause, and skip tracks on YouTube Music. Control your current listening session using simple commands like 'next' or 'previous'.

Instructions

pause, play (resume), toggle, next or previous.

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": {
      "action": "<action>"
    },
    "name": "music_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses almost nothing: no indication that pause is resumable, whether play resumes or restarts, how it interacts with the current queue/track, or what happens on failure. The only nugget is the parenthetical 'play (resume)', which is a small behavioral clarification.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short with no wasted words, but it is a sentence fragment rather than a front-loaded sentence, and its brevity borders on under-specification rather than earning each token.

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

Completeness2/5

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

For a mutation-style playback control tool with no annotations and no output schema, the description should clarify the resource affected, how each action changes player state, and any error/permission expectations. None of that is present, leaving the agent to guess at the tool's actual effect.

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?

The single 'action' enum already fully enumerates the allowed values in the schema, so the description largely repeats structured data. It does add one semantic note, 'play (resume)', clarifying that play resumes rather than restarts, which is marginal but non-zero added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the actions (pause, play/resume, toggle, next, previous), which maps to the enum and implies playback control. However, it never states a verb+resource ('control music playback') or what is being controlled, and it offers no differentiation from siblings like play_music or play_playlist, which overlap with the 'play' action.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of when to prefer this tool over play_music, play_playlist, or now_playing. The agent must infer entirely from the tool name and enum.

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