Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_delete_caption

Destructive

Delete an approved caption track from an owned YouTube video after confirming the preview and approval ID. Use it to remove unwanted captions while enforcing explicit change approval.

Instructions

Delete an approved owned caption track.

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": {
      "videoId": "<videoId>",
      "captionId": "<captionId>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_delete_caption"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
videoIdYesYouTube video ID (11 characters), e.g. dQw4w9WgXcQ.
captionIdYesCaption track ID, from youtube_list_caption_tracks.
approvalIdYesApproval ID from the youtube_preflight_caption_delete preview, after approving it with youtube_approve.

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_caption_delete preview, after approving it with youtube_approve."
    • addedInput schema / properties / captionId / description
      Added value: +"Caption track ID, from youtube_list_caption_tracks."
    • 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 / videoId / description
      Added value: +"YouTube video ID (11 characters), e.g. dQw4w9WgXcQ."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the description does not need to establish that this is a destructive mutation. It adds the 'approved owned' precondition, which is real context beyond annotations, but omits irreversibility/undo and the confirm-gate behavior that lives only in the schema.

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 no filler and the key constraint ('approved owned') front-loaded. It is appropriately sized, though a second sentence on the approval workflow would have earned its place.

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 destructive multi-step workflow tool, the description leaves the preflight→approve→delete chain and the confirm gate entirely to the schema. With destructiveHint and a fully-described schema, calling it correctly is still possible, so it is minimally adequate but not self-sufficient.

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 all four parameters (including confirm, videoId, captionId, approvalId) are fully documented in the schema itself. The description adds no additional parameter meaning, which is acceptable at the baseline but not additive.

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 gives a specific verb and resource (delete + caption track) plus a meaningful qualifier ('approved owned'), which tells the agent it operates on a caption the account owns after approval. It does not name or distinguish itself from youtube_preflight_caption_delete, so the sibling differentiation is only implicit.

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 the tool must be preceded by a preflight/approve cycle, but the description never states it, never names youtube_preflight_caption_delete as the prerequisite, and never distinguishes the execute step from the preview step. Usage is only implied, and only if the agent reads the schema's approvalId text.

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