yt-mcp

Overview Schema Source Related Servers Discussions Admin

Create a private radio playlist

create_private_radio_playlist

Generate a private YouTube Music playlist from a song-radio queue based on a query. Specify a title and optional description to save fresh radio recommendations directly to your connected account.

Instructions

Create a private playlist from a fresh song-radio queue in the connected account.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`query`	Yes
`title`	Yes
`description`	No	Created by yt-mcp.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`seed`	Yes
`title`	Yes
`tracks`	Yes
`requested`	Yes
`playlistId`	Yes
`trackCount`	Yes
`privacyStatus`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Sep 13, 2026

addedOutput schema / $defs / TrackResult / properties / album

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Album"
+}

addedOutput schema / $defs / TrackResult / properties / duration_seconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Duration Seconds"
+}

changedOutput schema / $defs / TrackResult / required

Previous value: -[
-  "videoId",
-  "title",
-  "artists",
-  "duration",
-  "url"
-]New value: +[
+  "videoId",
+  "title",
+  "artists",
+  "album",
+  "duration",
+  "duration_seconds",
+  "url"
+]

First observedv0.1.0Sep 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds little beyond confirming it creates a playlist. It does mention 'fresh song-radio queue,' which hints at creating a new queue, but it doesn't disclose other traits like whether the playlist is immediately visible or if it requires an existing radio queue. Since annotations cover the safety profile, the description meets the minimum but doesn't enrich behavioral context.

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

Conciseness4/5

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

The description is a single, front-loaded sentence that states the action and the key context. It is efficient and free of filler. However, it could arguably be slightly more detailed without becoming verbose, but it does not waste words.

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?

Given the tool has 4 parameters (2 required), no parameter descriptions, and an output schema, the description is far from complete. It doesn't explain how to construct the arguments, what the 'fresh song-radio queue' means in practice, or how it differs from the multi-seed variant. The presence of an output schema does not help with input construction. An agent would struggle to call this tool correctly without additional information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the parameters (title, query, limit, description) are documented in the schema. The description provides no information about what these parameters mean or how to use them. An agent would have to guess that 'query' is the seed song and 'title' is the playlist name, which is not obvious. The description completely fails to compensate for the missing schema documentation.

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?

The description uses a specific verb ('Create') and a specific resource ('private playlist') and adds a distinguishing context: 'from a fresh song-radio queue in the connected account.' This clearly separates it from sibling create_private_multi_seed_radio_playlist, which implies a multi-seed radio. The purpose is unambiguous and actionable.

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?

The description implies a use case (creating a private playlist from a single song-radio queue) but does not explicitly state when to choose this tool over the multi-seed sibling or get_song_radio. There is no mention of alternatives or exclusions. The context is present but not formalized, so an agent might need to infer the distinction.

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

Deploy Server