Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_delete_playlist

Destructive

Preview deletion of an owned YouTube playlist by playlist ID to verify the target before confirming removal.

Instructions

Read and preview deletion of 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>"
    },
    "name": "youtube_preflight_delete_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / playlistId / description
      Added value: +"YouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx."
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior1/5

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

The description says 'Read and preview deletion,' which signals a non-mutating preflight, while the annotation declares destructiveHint=true. That is a direct conflict about whether the tool itself can destructively alter state. The description otherwise adds little about permissions or what the preview returns.

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?

A single short sentence, front-loaded and free of repetition. It does not waste tokens or bury the key distinction.

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 one-parameter preflight tool, the schema covers the input and annotations cover safety, but the description omits what the preview returns and how it relates to the actual deletion tool. With no output schema, that omission matters more.

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?

The sole playlistId parameter is fully documented in the schema (100% coverage) with an example. The description adds no format, constraint, or semantic detail beyond what the schema already provides.

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 and resource: 'Read and preview deletion of an owned playlist.' This makes clear it is a preflight/preview operation rather than the actual delete, though it does not explicitly name the sibling youtube_delete_playlist.

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 'preview' implies this should be used before deletion, but the description never states when to choose it over youtube_delete_playlist or what prerequisites are needed. Usage is inferred rather than explicit.

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