Skip to main content
Glama

delete_video

Permanently delete a YouTube video by providing its ID and confirming the exact title to prevent accidental deletion.

Instructions

Permanently delete a video. Requires confirm_video_title to match the video's current title exactly — guards against deleting the wrong video by ID. Deletion is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idYesVideo ID to delete.
confirm_video_titleYesExact current title of the video. Must match what YouTube returns to proceed — prevents accidental deletion of the wrong video.

Implementation Reference

  • client.deleteVideo() — helper that makes a DELETE HTTP request to the YouTube Data API's /videos endpoint with the given video ID.
    deleteVideo(videoId: string): Promise<void> {
      const url = new URL(`${DATA_API}/videos`);
      url.searchParams.set("id", videoId);
      return this.request<void>(url.toString(), { method: "DELETE" });
    }
Behavior4/5

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

Discloses irreversible deletion and the confirmation guard, which is key behavioral context. Without annotations, this provides necessary transparency, though permissions or side effects are omitted.

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?

Two sentences, front-loaded with core purpose, no wasted words.

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 simple tool with 2 fully-described parameters and no output schema, the description covers all essential aspects: purpose, safety guard, and irreversibility.

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?

Adds meaning beyond schema by explaining why confirm_video_title is needed (prevents accidental deletion) and that deletion is irreversible. Schema descriptions are clear, but description enriches understanding.

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?

Description clearly states 'Permanently delete a video', using specific verb and resource. Distinguishes from siblings like 'delete_caption' which deletes a different resource.

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?

No explicit when-to-use or when-not-to-use guidance. While the safety guard implies careful usage, alternative tools or conditions are not mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miller-joe/youtube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server