Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_caption_delete

Destructive

Preview deletion of an owned YouTube caption track before committing changes, so you can verify the video and caption track IDs.

Instructions

Preview deletion of an 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>"
    },
    "name": "youtube_preflight_caption_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesYouTube video ID (11 characters), e.g. dQw4w9WgXcQ.
captionIdYesCaption track ID, from youtube_list_caption_tracks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / captionId / description
      Added value: +"Caption track ID, from youtube_list_caption_tracks."
    • addedInput schema / properties / videoId / description
      Added value: +"YouTube video ID (11 characters), e.g. dQw4w9WgXcQ."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The destructiveHint=true annotation already signals the dangerous intent this previews. The description adds the ownership constraint, but is silent on what a preview actually produces (a confirmation token? a summary?) and on whether calling it has any side effects, which is the key behavioral unknown for a preflight tool.

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 front-loaded sentence with no filler. It is efficient, though its brevity shades into under-specification for a two-step destructive workflow.

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?

No output schema exists, so the description must explain what the preview returns and how it connects to youtube_delete_caption; it does neither. For a destructive preflight step in a 70+ tool surface, an agent cannot tell from this text how to complete the deletion safely.

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%, with both videoId and captionId documented, including the pointer to youtube_list_caption_tracks as the source of captionId. The description adds nothing beyond that, so the 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 (preview) plus resource (caption track) and adds the 'owned' scope restriction, which tells an agent this only applies to videos the authenticated user controls. It does not name youtube_delete_caption as the commit counterpart, so sibling differentiation is left implicit despite the obvious preflight/commit naming pattern.

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 precede yt_del youtube_delete_caption, but the description never says so, never states that the actual deletion requires the separate tool, and gives no prerequisites. Usage is inferable only from the name convention shared with other siblings.

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