Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_delete_playlist

Destructive

Deletes an owned YouTube playlist only after an approved preflight preview, requiring an approval ID and explicit confirmation.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
approvalIdYesApproval ID from the youtube_preflight_delete_playlist preview, after approving it with youtube_approve.
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_delete_playlist 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."
  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?

destructiveHint=true already declares the operation is irreversible in kind, so the description need not repeat that. It does add the useful workflow constraint that deletion is gated on prior approval, but it omits whether playlist items are also removed, whether the playlist must be owned, or what happens if the approval is stale.

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 five-word sentence with the verb and scoping qualifiers front-loaded and zero filler. It is efficient, though terse enough that it leans on the schema for nearly all operational detail.

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, gated mutation the critical safety context is split across a destructiveHint annotation and detailed schema parameter descriptions, so an agent can call this correctly. The one gap is that the preflight/approve sequencing is not restated in the description itself, only inferable from 'approved'.

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 are unusually rich: confirm must be true and set only after approval, approvalId comes from the preflight preview, playlistId has a format example. The description adds nothing beyond that, 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?

The description states a specific verb ('Delete') and resource ('playlist') and adds qualifying scope ('approved owned'), which tells an agent this is the execution step, not a preview. It does not name the sibling it is paired with (youtube_preflight_delete_playlist), but the intent is still unambiguous.

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?

'Approved' implies the preflight-then-approve prerequisite, but the description never states that the agent must first call youtube_preflight_delete_playlist and youtube_approve, nor what to do if approval is missing. That guidance exists only inside the parameter descriptions, so the description itself gives implied rather than explicit usage direction.

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