Skip to main content
Glama
Sign In
mateai-youtube

mateai-youtube

by mategog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

yt_delete_video

Destructive

Permanently deletes a YouTube video after exact-title confirmation; use it only for irreversible removal, not for hiding videos—set privacy via yt_update_video instead.

Instructions

DANGEROUS — the server asks the user in a confirmation dialog before this runs. PERMANENTLY delete one of the channel's videos (videos.delete, ~50 quota units). Irreversible: views, watch hours and comments are lost. To merely hide a video use yt_update_video with privacy_status. Refuses unless confirm_title exactly equals the video's current title.

Input Schema

NameRequiredDescriptionDefault
video_idYes11-character YouTube video ID.
confirm_titleYesExact current title of the video, as a deliberate confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • removedInput schema / properties / user_confirmed
      Removed value: -{
-  "description": "Set true ONLY after the user explicitly approved this exact action in chat. Never set it on your own.",
-  "type": "boolean"
-}
  2. Addedv0.7.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the generic destructive hint, the description reveals critical behavioral details such as the server requiring a confirmation dialog, the irreversible nature of the action, and the associated cost (~50 quota units). This provides the agent with essential operational and risk management context.

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?

The description is highly dense and efficient; every word contributes to reducing ambiguity for the agent. Critical warnings ('DANGEROUS', 'PERMANENTLY') are front-loaded, and the logical flow moves from risk to execution to alternative usage.

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?

Given that this is a high-stakes, destructive tool, the definition is perfectly complete. It addresses safety protocols (confirmation dialog), irreversible consequences, resource costs, and necessary interaction rules with related functions.

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?

While the input schema covers parameter types and requirements, the description adds semantic value by defining the necessity of `confirm_title` as a deliberate validation mechanism. This reinforces the schema definition but provides crucial 'why' context that structured data lacks.

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?

The description clearly states the primary function as 'Permanently delete' a video and explicitly distinguishes itself from `yt_update_video` by noting it is used when the goal is deletion, not merely hiding content.

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

Usage Guidelines5/5

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

It provides explicit usage rules by naming the correct sibling tool (`yt_update_video`) for non-destructive hiding. Furthermore, it specifies the strict requirement that the function refuses to run unless `confirm_title` exactly matches the current video title.

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