YouTube Music MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_API_KEY | Yes | Google Youtube API Key required to access the YouTube Music API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchTrackC | Search for tracks on YouTube Music by name. |
| playTrackA | Search for a track on YouTube Music and open the top result in the default browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have overlapping purposes that could cause confusion. Both 'playTrack' and 'searchTrack' involve searching for tracks on YouTube Music, with 'playTrack' additionally opening the top result in a browser. An agent might misselect between them when the intent is ambiguous, such as wanting to search without playing or vice versa, as the descriptions don't clearly delineate distinct use cases.
The tool names follow a consistent pattern throughout. Both use camelCase with a verb-noun structure ('playTrack' and 'searchTrack'), making them predictable and readable. There are no deviations or mixed conventions, which aids in clarity and usability.
The tool count of 2 feels too thin for a YouTube Music server's apparent scope. With only search and play functionality, there are obvious gaps like managing playlists, controlling playback, or accessing user data. This limited set may hinder agents from performing common music-related tasks, indicating an incomplete surface for the domain.
The tool surface is severely incomplete for a YouTube Music domain. It only covers searching and playing tracks, missing essential operations such as pausing, skipping, volume control, playlist management, or user authentication. These gaps will likely cause agent failures when attempting broader music interactions, as the current tools don't support a full lifecycle or common workflows.