YouTube MCP Server

Youtube List Playlist Items

youtube_list_playlist_items

List the videos in any playlist, in playlist order — one shared-pool unit per page.

Instructions

List the videos in any playlist, in playlist order — one shared-pool unit per page.

Unlike youtube_list_channel_videos this needs no channel: give it the playlist ID (from youtube_get_channel's uploads_playlist_id, youtube_get_playlist, a video's page, or the user) and it walks that playlist. Each item carries video_id, title, channel_title, its position in the playlist, and published_at, which is when the video was added to this playlist — a playlist keeps its own order and its own add-dates, so these are not the videos' publish dates.

Costs one unit from the shared 10,000-unit pool per page, the large pool — never the scarce 100/day search.list bucket, which this tool does not touch. Items carry no view counts; get those from youtube_get_video_stats (its own bucket).

page_token is YouTube's opaque nextPageToken, handed straight back exactly as received — never a page number or an offset, and never the integer character cursor from youtube_get_transcript (a different mechanism entirely). An empty playlist returns items: [] with no error: that is the real answer, not a failure. A private playlist fails with an error that says so and is distinct from "does not exist"; retrying helps neither.

Input Schema

Name	Required	Description	Default
`page_token`	No
`max_results`	No
`playlist_id`	Yes

Output Schema

Name	Required	Description	Default
`items`	No
`playlist_id`	Yes
`next_page_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Oct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: quota cost of one shared-pool unit per page (10,000 shared vs the 100/day search bucket, which it does not touch), empty playlist returns `items: []` without error, private-playlist errors are distinct from not-found and are not retryable. It also clarifies that `published_at` is playlist add-date, not video publish date — a genuine semantic trap.

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?

Front-loaded with the purpose and alternative, and nearly every sentence carries operational information. Slightly over-rich in asides (the parenthetical about the transcript cursor mechanism), and the markdown emphasis is noisy, but nothing is truly filler.

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

Completeness5/5

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

An output schema exists, yet the description still names the item fields and their meaning, covers quota, pagination, and both empty and private-playlist edge cases. An agent has everything needed to call it correctly and interpret failures.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does for two of three params: `page_token` is described at length as an opaque `nextPageToken` never a page number and explicitly not the transcript character cursor; `playlist_id` sources are enumerated. `max_results` (default 50, max 50) is never mentioned, leaving the page-size control undocumented in both places.

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?

Opens with a specific verb and resource ('List the videos in *any* playlist, in playlist order') and immediately names the sibling it is not (`youtube_list_channel_videos`), explaining that no channel is required. An agent can distinguish this from every sibling without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: get `playlist_id` from `youtube_get_channel`'s `uploads_playlist_id`, `youtube_get_playlist`, a video's page, or the user. It also names the alternative for the channel-scoped case and points to `youtube_get_video_stats` for view counts this tool does not return.

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

Deploy Server