Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_add_playlist_item

Destructive

Preview adding a video to an owned YouTube playlist before committing the change; verify the playlist and video IDs first.

Instructions

Read and preview adding a video to an owned 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>",
      "videoId": "<videoId>"
    },
    "name": "youtube_preflight_add_playlist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesID of the video to add to the playlist.
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / playlistId / description
      Added value: +"YouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx."
    • addedInput schema / properties / videoId / description
      Added value: +"ID of the video to add to the playlist."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

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

Annotations declare destructiveHint=true, while the description describes the tool as 'Read and preview', which strongly implies a non-destructive operation. No clarification is provided to resolve this contradiction about side effects.

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 front-loaded sentence with no wasted text. The phrase 'Read and preview' is slightly awkward, but the description remains concise.

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

Completeness2/5

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

For a preflight tool paired with youtube_add_playlist_item, it omits the relationship to the actual mutation, expected preview behavior, and any side-effect clarification. The destructiveHint contradiction leaves the agent uncertain about what this tool actually does.

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%, so both playlistId and videoId are already documented. The description only loosely maps them to 'video' and 'owned playlist' and adds no syntax, constraints, or examples beyond the schema.

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?

States a specific action and resource: preview adding a video to an owned playlist. The 'preflight' framing distinguishes it from the mutation sibling youtube_add_playlist_item, though it does not explicitly name that counterpart.

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 description implies this is a preliminary check before using youtube_add_playlist_item, but it never explicitly states when to use this tool versus the actual add operation or whether it has side effects.

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