Skip to main content
Glama
Sign In
YouTube MCP Server

YouTube MCP Server

by danieldoalto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

playlists_getPlaylistItems

Retrieve videos from a YouTube playlist by providing the playlist ID. Control the result count with an optional limit.

Instructions

Get videos in a YouTube playlist

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playlistId": "<playlistId>"
    },
    "name": "playlists_getPlaylistItems"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of results to return
playlistIdYesThe YouTube playlist ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, yet the description only states 'get' without disclosing behaviors like pagination, rate limits, authentication needs, or default parameter values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but lacks structure; no front-loading of key constraints or examples. Could be expanded slightly for clarity.

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 simple read tool with 2 parameters and no output schema, the description is minimal. Missing details like required parameter implication (playlistId is required in schema but not stated in description) and default for maxResults. Adequate but not complete.

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 maxResults and playlistId documented. The description adds no additional semantic meaning beyond the schema, so baseline 3 is appropriate.

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 'Get videos in a YouTube playlist' clearly states the action (get), resource (videos), and context (playlist). It distinguishes from siblings like playlists_getPlaylist and videos_getVideo.

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 guidance on when to use this tool versus alternatives such as playlists_getPlaylist or videos_searchVideos. Lacks context for preferred use cases.

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