Skip to main content
Glama
youtube-playlists-mcp

youtube-playlists-mcp

by kvechkanov

list_my_playlists

List the authenticated user's YouTube playlists with IDs, titles, item counts, and privacy settings, and use page tokens to fetch more results.

Instructions

List the authenticated user's YouTube playlists (id, title, item count, privacy). Quota cost: 1 unit per call. Returns nextPageToken when more pages exist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTokenNonextPageToken from a previous call.
maxResultsNoPage size, 1-50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and delivers real behavioral facts: quota cost of 1 unit per call and the presence of nextPageToken when more pages exist. It does not cover auth scope requirements explicitly beyond "authenticated user", or whether special auto-generated playlists (e.g. Watch Later) are included.

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 sentences, both front-loaded with the essentials: what is returned first, then quota and pagination. Every clause carries information an agent needs and there is 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?

For a simple two-parameter read tool with fully described schema and no output schema, the definition covers purpose, scope, returned fields, quota cost, and pagination sufficiently to call it correctly. Minor gaps remain around auth scope and default page size behavior, but nothing blocking.

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%, so pageToken and maxResults are already documented with their roles and bounds. The description's note about nextPageToken adds slight connective meaning between the return value and the pageToken input, but no new parameter semantics beyond the 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?

States a specific verb and resource ("List the authenticated user's YouTube playlists") and enumerates the returned fields (id, title, item count, privacy). This is clearly separable from list_playlist_items, which operates on the contents of a single playlist rather than the user's playlist collection.

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?

The scoping phrase "authenticated user's" implicitly signals this is the entry point for browsing one's own playlists, but there is no explicit when-to-use guidance, no mention of when to prefer search_videos or list_playlist_items, and no stated prerequisites. Usage is inferable rather than instructed.

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