Skip to main content
Glama
Sign In
mcp-youtube

mcp-youtube

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

YouTube: List Playlists

youtube_list_playlists
Read-only

List a YouTube channel's playlists, including private ones, with IDs, titles, privacy, and item counts. Use playlist IDs for adding videos or uploading content.

Instructions

This channel's playlists, including private ones: id, title, privacy and item count. The id is what youtube_add_to_playlist and youtube_upload_video's playlistId take. Costs 1 quota unit per page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results per page (1-50, YouTube's own cap). Defaults to 25.
page_tokenNoThe `next_page_token` from the previous call, to fetch the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds meaningful extras the annotations cannot convey: private playlists are included (implying authenticated channel scope), results are paginated, and each page costs 1 quota unit. It stops short of stating whether results are ordered or whether an empty channel returns an empty list.

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, front-loaded with scope and returned fields, then the practical id linkage, then quota cost. Nothing is wasted and nothing is buried.

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?

There is no output schema, so the description compensates by naming the returned fields explicitly. Combined with quota cost, pagination, and the cross-tool id reference, an agent has everything needed to call it correctly and use the result.

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 both limit and page_token fully documented in the schema, so the baseline is 3. The phrase 'per page' reinforces the pagination model but adds no syntax or format detail beyond what the schema already states.

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 the exact resource (this channel's playlists), an important scope qualifier (including private ones), and enumerates the returned fields (id, title, privacy, item count). An agent can distinguish it from youtube_list_videos and youtube_list_categories without opening any schema.

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?

Provides a concrete downstream-use cue: the returned id is what youtube_add_to_playlist and youtube_upload_video's playlistId accept, which tells the agent when this tool is the prerequisite step. It does not explicitly contrast with the other list tools, but the scope statement makes the choice largely self-evident.

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