Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

List My Playlists

youtube_list_playlists
Read-onlyIdempotent

List all playlists owned by your YouTube channel with support for pagination and adjustable result count.

Instructions

List all playlists belonging to the authenticated channel.

Args

  • maxResults (integer 1–50, default 25): Number of playlists to return per page.

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

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

Returns JSON shape:

{
  "playlists": [
    {
      "id": "PL...",
      "title": "My Playlist",
      "description": "...",
      "privacyStatus": "public" | "private" | "unlisted",
      "itemCount": 12,
      "publishedAt": "2024-01-01T00:00:00Z"
    }
  ],
  "nextPageToken": "...",
  "totalResults": 42
}

Examples

  • List first page: youtube_list_playlists()

  • Page 2: youtube_list_playlists({ pageToken: "..." })

Errors

  • 401/403 → re-run npm run auth; check OAuth scopes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoNumber of playlists to return (1–50, default 25).
pageTokenNoPagination cursor returned from a previous call.
response_formatNoOutput format: "markdown" (default) or "json".markdown
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds valuable context: authentication requirement, pagination details, output format, and specific error codes (401/403). No contradictions.

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?

The description is well-organized with clear sections (Args, Returns, Examples, Errors). It is concise, each sentence adds value, and it avoids unnecessary details.

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?

Despite lacking an output schema in the tool definition, the description provides a complete JSON shape of the return value. It includes examples, error handling, and covers all parameters. The tool is fully documented for an agent to use correctly.

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 baseline is 3. The description's parameter explanations largely repeat the schema (e.g., 'Number of playlists to return per page'), adding little beyond the schema's definitions. No new semantic information is provided.

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?

The description clearly states 'List all playlists belonging to the authenticated channel,' which is a specific verb and resource. It distinguishes from siblings like youtube_get_playlist (single playlist) and youtube_create_playlist (create).

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 provides clear context for when to use the tool: listing all playlists of the authenticated user. It does not explicitly mention alternatives, but the scope and examples imply appropriate use. Error handling hints at prerequisites (authentication).

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