Skip to main content
Glama
thenavidm

YouTube MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a video

delete_video
Destructive

Permanently remove a video from a connected YouTube channel. Use when a user asks to delete a specific video, setting confirm to true because the action cannot be undone.

Instructions

Permanently delete a video from a connected channel. YouTube removes it immediately: there is no trash, no undo, and the views, comments and URL go with it. Needs confirm: true.

Input Schema

NameRequiredDescriptionDefault
accountNoWhich connected channel to act on (name or @handle). Required when more than one is connected: without it the call fails and lists the choices rather than picking one.
confirmNoSet true only when the user asked for exactly this action.
video_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true. This cannot be undone."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds rich detail beyond annotations: no trash, no undo, collateral loss of views, comments and URL, and the required confirm flag for authorization. This goes well past the destructiveHint and idempotentHint signals.

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?

Three tight sentences, front-loaded with the action and its irreversible consequence. Every clause earns its place.

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

Completeness5/5

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

For a destructive, irreversible tool with no output schema, the description covers consequence, irreversibility, and the confirm gate, which is what an agent needs to invoke it responsibly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% with formal descriptions on account and confirm. The description reinforces the confirm requirement, adding value on the highest-risk parameter, though it doesn't detail video_id format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (delete) and resource (video), plus scope (from a connected channel). Distinct from the sibling update_video by its permanently destructive nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage instructions including a required confirm:true gate, implying this is not for reversible changes. Does not name explicit alternatives, but for a terminal destructive action the guardrail is the relevant guidance.

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