Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_list_playlist_items

Read-only

Retrieve items from an owned YouTube playlist, with pagination via pageToken and maxResults to control the number of results returned.

Instructions

List items from an owned creator playlist.

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": {
      "playlistId": "<playlistId>"
    },
    "name": "youtube_list_playlist_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTokenNoPage token from the nextPageToken of a previous response, to fetch the next page.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of items to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / pageToken / description
      Added value: +"Page token from the nextPageToken of a previous response, to fetch the next page."
    • addedInput schema / properties / playlistId / description
      Added value: +"YouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already declares the read-only safety profile, so the description's lower burden is met. It adds the ownership constraint (playlist must belong to the authenticated creator), which is real context, but says nothing about auth failure modes, pagination behavior, or result ordering.

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?

A single front-loaded sentence with no filler; the scope qualifier arrives before any implied caveats. It is efficient, though so terse that it omits any routing or return-value context that could have been added without bloat.

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?

With 3 flat parameters fully documented in-schema, readOnly annotations, and no output schema, the description covers purpose and scope adequately for a simple list tool. The missing piece is what a 'playlist item' contains and whether pagination is expected, which no output schema covers.

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 description coverage is 100%, with pageToken, maxResults (1-50), and playlistId each documented in-schema including an example format. The description contributes nothing parameter-specific, which is acceptable at this coverage level but warrants only the baseline 3.

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?

Specific verb+resource ('List items from ... playlist') with a scoping qualifier ('owned creator'). An agent can distinguish it from get_playlist metadata retrieval, though the description never names the closest sibling (youtube_get_playlist / youtube_list_playlists) to sharpen the boundary.

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?

'Owned creator playlist' implies the only valid context (authenticated creator operating on their own playlists), which implicitly rules out arbitrary public playlists. However, there is no explicit statement of when to choose this over youtube_get_playlist (metadata) or youtube_list_playlists (enumeration), and no prerequisite/auth guidance.

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

Deploy Server

Other Tools