Skip to main content
Glama
Sign In
YouTube Playlist MCP

YouTube Playlist MCP

by haktanonur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List my playlists

list_my_playlists
Read-only

Retrieve playlists from an authorized YouTube account, 50 per page, to inspect available playlists for AI-driven search, selection, or management tasks.

Instructions

List playlists in the authorized YouTube account (50 per page, 1 quota unit). Read-only.

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
page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so 'Read-only' is largely redundant. The description does add genuinely new context — 50 items per page and 1 quota unit per call — which helps an agent plan pagination and cost. However, it never explains how paging terminates or that page_token values should not be reused.

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 compact sentence with scope, page size, and quota cost front-loaded; nothing bloats it. The redundant 'Read-only' is the only waste and is minor.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool the description is close to adequate: purpose, cost, and page size are covered. The pagination input is unexplained and there is no output schema to fall back on, so the agent lacks the full contract for follow-up calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single page_token parameter is documented nowhere. The description mentions paging ('50 per page') but never says what page_token is, where it comes from, or that it is optional for the first call — leaving the agent to guess the contract for the only input.

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?

Clear verb and resource ('List playlists') scoped to the authorized account, which separates it from a generic search. It does not explicitly contrast with siblings like preview_playlist or get_playlist_items, so differentiation relies on the agent's inference.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, and no routing to alternatives such as preview_playlist for inspection or get_playlist_items for contents. The quota cost note is useful operational context but does not tell the agent when this tool is the right choice.

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