Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

List Playlist Items

youtube_list_playlist_items
Read-onlyIdempotent

Retrieve videos inside a YouTube playlist with pagination support. Use playlist ID to get items, optionally paginate with pageToken.

Instructions

List the videos inside a playlist, with pagination support.

Args

  • playlistId (string, required): Playlist ID to list items from.

  • maxResults (integer 1–50, default 25): Items per page.

  • pageToken (string, optional): Pagination cursor from a previous call's nextPageToken.

  • response_format ("markdown" | "json", default "markdown"): Output format.

Returns JSON shape:

{
  "playlistId": "PL...",
  "items": [
    {
      "playlistItemId": "PLitem...",
      "position": 0,
      "videoId": "dQw4w9WgXcQ",
      "title": "Video Title",
      "description": "...",
      "publishedAt": "2024-01-01T00:00:00Z",
      "videoOwnerChannelTitle": "Channel Name"
    }
  ],
  "nextPageToken": "...",
  "totalResults": 50
}

Examples

  • youtube_list_playlist_items({ playlistId: "PL..." })

  • Next page: youtube_list_playlist_items({ playlistId: "PL...", pageToken: "..." })

Errors

  • 404 → playlist not found.

  • 403 → no access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playlistIdYesPlaylist ID whose items to list.
maxResultsNoItems per page (1–50, default 25).
pageTokenNoPagination cursor from a previous call.
response_formatNoOutput format: "markdown" (default) or "json".markdown
Behavior4/5

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

Adds pagination details, output shape, and error codes beyond annotations (readOnlyHint, etc.). No contradiction.

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?

Well-organized with sections (Args, Returns, Examples, Errors). Concise and informative.

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?

Complete for a listing tool: covers all parameters, pagination, errors, output format. No missing context.

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 covers all 4 params; description adds usage examples and output format, enhancing meaning beyond schema.

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?

Clearly states 'List the videos inside a playlist, with pagination support.' Distinguishes from sibling tools like youtube_list_playlists by specifying playlist items.

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?

Implicitly conveys when to use (listing playlist items) with examples and error handling, but could explicitly differentiate from add/remove operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server