Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_remove_playlist_item

Destructive

Preview the removal of an immutable playlist item from YouTube. Check if a specific item can be successfully deleted from a playlist before executing the change.

Instructions

Read and preview removal of an immutable playlist item.

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>",
      "playlistItemId": "<playlistItemId>"
    },
    "name": "youtube_preflight_remove_playlist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.
playlistItemIdYesPlaylist item ID (not the video ID), from youtube_list_playlist_items.

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 / playlistItemId / description
      Added value: +"Playlist item ID (not the video ID), from youtube_list_playlist_items."
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true; the description adds the useful fact that the tool reads and previews rather than mutates, and that playlist items are immutable (explaining why removal, not editing, is the only option). However there is mild tension between 'read and preview' and destructiveHint=true, and the description never clarifies what the preview actually returns or whether it has any side effect.

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 well-formed sentence with no filler and the read/preview intent front-loaded. It is efficient but so terse that it reads as under-specification rather than deliberate concision.

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 two-required-parameter tool with no output schema, the description should explain what the preview returns (item snapshot, validation errors, confirmation token) and what the agent does next. Nothing about the preview payload or the follow-up call is covered, leaving a real gap for a preview-only tool.

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% and both parameters carry their own descriptions, including the important note that playlistItemId is not the video ID and comes from youtube_list_playlist_items. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 verb pair ('Read and preview') plus the exact resource ('removal of an immutable playlist item'), which is clearly distinguishable from mutation siblings like youtube_remove_playlist_item by the preview framing. It does not explicitly name the sibling it pairs with, so the differentiation is implied rather than stated.

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?

The word 'preflight/preview' hints at a two-step workflow, but the description never says when this tool should be called instead of youtube_remove_playlist_item, whether it is required before removal, or what to do with the preview result. In a server with ~30 preflight siblings, an agent gets no explicit routing guidance.

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