Fetch YouTube playlist metadata and normalized video items by ID or URL. Supports pagination via continuation token for retrieving large playlists.
Retrieve playlist metadata and items. Returns playlist metadata, normalized video items, and an optional continuation token for pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | YouTube playlist ID or full playlist URL | |
| continuation_token | No | Pagination token returned by a previous request |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses return structure (metadata, items, continuation token) and pagination, but does not mention access restrictions (e.g., private playlists) or authentication needs.
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?
Single sentence, front-loaded with verb, zero waste. Efficiently communicates purpose and output.
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?
No output schema exists, so description must explain return values. It achieves this by stating returns metadata, normalized video items, and continuation token. Adequate for a playlist tool, though more detail on item structure could help.
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 coverage is 100%, and the description adds no additional meaning beyond what the input schema already provides for both parameters. Baseline 3 is appropriate.
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 explicitly states 'Retrieve playlist metadata and items', clearly identifying the verb and resource. It distinguishes itself from sibling tools like youtube_video and youtube_search by focusing on playlists.
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?
The description implies usage for retrieving a specific playlist's content, but does not explicitly state when to use it versus alternatives like youtube_channel_playlists. It provides clear context but lacks exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.