Skip to main content
Glama
Sign In
youtube-playlists-mcp

youtube-playlists-mcp

by kvechkanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_playlist_items

Retrieves the videos in a YouTube playlist, returning each item's playlist item ID and video ID plus pagination tokens so you can review contents or prepare items for removal.

Instructions

List the videos in a playlist. Each item includes playlistItemId (needed for remove_playlist_item) and videoId. Quota cost: 1 unit per call (50 items per page). Returns nextPageToken when more pages exist.

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": "list_playlist_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTokenNonextPageToken from a previous call.
playlistIdYesPlaylist ID (or a URL containing ?list=...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does well: it discloses quota cost (1 unit per call), page size (50 items), and pagination behavior via nextPageToken. It does not mention permission/auth requirements or whether private playlists are accessible, which is the main remaining gap.

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?

Three short sentences, front-loaded with what the tool returns, then operational constraints. Every sentence contributes distinct information — return fields, quota cost, and pagination — with no filler.

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?

There is no output schema and no annotations, so the description appropriately compensates by naming the returned fields and the pagination token, plus quota cost. It is nearly complete; only permission/visibility behavior for private playlists is left unaddressed.

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%, and the schema already explains pageToken as coming from a previous call and playlistId as accepting a URL with ?list=. The description reinforces the pagination link but adds no new syntax or constraint detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("List the videos in a playlist") and implicitly separates itself from list_my_playlists by scoping to items inside a single playlist. Naming the returned identifiers (playlistItemId, videoId) further confirms it returns playlist contents rather than playlist metadata.

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

Usage Guidelines4/5

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

The description gives clear context for use and, notably, states that playlistItemId is "needed for remove_playlist_item", which routes the agent into the correct follow-up workflow. It stops short of explicit when-not guidance or naming list_my_playlists as the alternative for enumerating playlists, so it is not a full 5.

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