Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

List videos in a playlist

get_playlist_items
Read-onlyIdempotent

Retrieve videos from a YouTube playlist in playlist order, including playlist details on the first page and paginated results for browsing large playlists.

Instructions

Videos in a playlist, in playlist order, plus the playlist's own details on the first page. Paginated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_tokenNonext_page_token from a previous call, for the next page.
max_resultsNoItems per page, 1-50.
playlist_idYesThe playlist ID (PL..., UU..., etc.).
include_statsNoInclude views, likes, comments and duration.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description contributes genuinely useful behavior beyond that: results come back in playlist order, and the playlist's own details appear only on the first page — an asymmetry an agent would otherwise not know. It stops short of describing page-size limits or what happens with an invalid playlist_id.

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

Conciseness5/5

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

Two short sentences, front-loaded with the resource and scope, and no filler. Each clause carries distinct information: order, first-page metadata, and pagination.

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

Completeness4/5

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

For a four-parameter read tool with a 100% described schema and an output schema, the description covers the non-obvious behavior (ordering, first-page-only playlist details, pagination). The main omission is any hint that the call fails or returns empty for a nonexistent or empty playlist.

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

Parameters3/5

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

Schema coverage is 100%, with page_token, max_results, playlist_id and include_stats all self-documented including ranges and defaults. The description's only added meaning is that pagination exists and that the first page carries extra material; it adds nothing about how max_results or include_stats affect the shape of results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Identifies a specific resource (a given playlist's videos) and adds two distinguishing traits: playlist order and playlist metadata on the first page. It is a noun phrase rather than a verb, but an agent can tell it apart from list_playlists or search_videos by the 'videos in a playlist' framing.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no comparison to alternatives such as search_videos or list_playlists. The 'Paginated' note implies you continue calling it with a page token, but the agent must infer that a playlist_id is presupposed rather than being told.

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