get_song_radioFind a song on YouTube Music and get an ordered list of radio recommendations based on the first matching track.
Get YouTube Music's ordered radio recommendations around the first song match.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| seed | Yes | ||
| tracks | Yes | ||
| returned | Yes | ||
| requested | Yes |
Changes observed during successful MCP inspections.
v0.3.0Output schema / $defs / TrackResult / properties / albumAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "title": "Album"
+}Output schema / $defs / TrackResult / properties / duration_secondsAdded value: +{
+ "anyOf": [
+ {
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "title": "Duration Seconds"
+}Output schema / $defs / TrackResult / requiredPrevious value: -[
- "videoId",
- "title",
- "artists",
- "duration",
- "url"
-]New value: +[
+ "videoId",
+ "title",
+ "artists",
+ "album",
+ "duration",
+ "duration_seconds",
+ "url"
+]v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, non-destructive behavior, so the description only needs to add selection and ordering semantics. 'Ordered' reveals result ordering, and 'around the first song match' explains how the query is resolved. This adds value beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no filler. It front-loads the key resource and operation before adding the qualifier, making it easy to scan and understand.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with an output schema and strong annotations, the description is largely sufficient. The remaining gaps—unexplained limit semantics and lack of explicit alternative guidance—are minor but prevent a perfect score.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It implicitly clarifies that query is the song search whose first match seeds the radio, but it says nothing about limit, leaving its meaning—number of tracks, number of radio items, or search results—to inference from the default of 30.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), a clear resource ('YouTube Music song radio'), and a precise behavior ('ordered radio recommendations around the first song match'). The single-seed 'first song match' phrasing distinguishes it from siblings like get_multi_seed_radio and search_songs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance is provided. The phrase 'around the first song match' implies a single-song seed, which indirectly separates it from get_multi_seed_radio, but the description does not directly name alternatives or state selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.