Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_remove_playlist_item

Destructive

Remove a specific playlist item from a YouTube playlist after approval. Use the playlist ID, item ID, and approval ID to execute the change.

Instructions

Remove an approved 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>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_remove_playlist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
approvalIdYesApproval ID from the youtube_preflight_remove_playlist_item preview, after approving it with youtube_approve.
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. Changed4 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_remove_playlist_item preview, after approving it with youtube_approve."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
    • 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

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds that the item must be 'approved' and 'immutable', signalling a mandatory approval gate before execution, but it doesn't state that the removal is irreversible or describe any failure modes. Useful but limited context beyond annotations.

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 short sentence with the verb front-loaded and zero wasted words. It is arguably over-terse, but nothing is redundant.

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

Completeness4/5

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

For a destructive tool, the schema fully explains the confirmation and approval gating and all IDs, so most of what an agent needs is present. The description itself is thin on the preflight prerequisite and irreversibility, but the rich schema largely compensates and no output schema is required.

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% and the parameter descriptions already explain confirm, approvalId provenance, and item ID sourcing in detail. The description contributes nothing about parameters, so baseline 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 (Remove) and resource (playlist item) with a qualifying 'approved immutable' scope that hints at the execution phase of an approval workflow, implicitly distinguishing it from youtube_preflight_remove_playlist_item. The phrase 'immutable playlist item' is slightly odd, but an agent can still identify the operation without opening the schema.

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 word 'approved' implies a prerequisite gate, but the description never explicitly says to run youtube_preflight_remove_playlist_item first or when this executes vs the preflight sibling. The when-to-use is only inferable, and the workflow detail is carried by the schema's parameter descriptions rather than the description itself.

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