youtube-kit

by eukosh

Overview Schema Source Related Servers Discussions Admin

Python

Local

Delete Comment

delete_comment

DestructiveIdempotent

Permanently delete one of your own comments or replies. Deleting a top-level comment deletes its replies.

Instructions

Permanently delete one of your own comments or replies. Deleting a top-level comment deletes its replies.

Others' comments on your videos can't be deleted, only rejected, which hides them. Without confirm, nothing is deleted and the error describes the comment.

Quota: 52 units.

Input Schema

Name	Required	Description
`comment`	Yes	Comment ID or link.
`confirm`	No	The comment ID again, passed only after the user has approved deleting this comment.
`my_channel`	No	Which of your logged-in channels to work on: UC… ID, @handle or exact title. Omit for the default channel.

Output Schema

Name	Required	Description
`id`	Yes
`kind`	Yes
`already_gone`	No	Nothing to delete: it didn't exist or was already deleted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.1Oct 22, 2026

changedOutput schema / properties / kind / enum

Previous value: -[
-  "video",
-  "playlist",
-  "comment",
-  "section"
-]New value: +[
+  "video",
+  "playlist",
+  "comment",
+  "section",
+  "caption"
+]

First observedv0.1.0Oct 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantive context they don't carry: the cascade behavior (deleting a top-level comment deletes its replies), the two-step confirmation guard and its failure mode, and the 52-unit quota cost. These are precisely the details an agent needs before invoking an irreversible write.

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?

Four short sentences, front-loaded with the destructive action and its scope, then exclusions, then the safety gate, then quota. Every sentence carries distinct operational information with no repetition of the schema.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to supply the irreversible-action semantics — cascade deletion, the confirm gate, quota, and the rejection alternative. All are present, leaving no meaningful gap for a destructive, three-parameter tool.

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 100%, so the baseline is 3; the description earns above baseline by explaining the consequence of the `confirm` parameter rather than just its format — omitting it is a safe no-op that returns an error describing the comment. It does not add anything about `my_channel` or the accepted ID/link formats for `comment`, which the schema already covers.

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 and resource ('Permanently delete one of your own comments or replies') and immediately bounds the scope to the caller's own comments. The second sentence distinguishes it from the sibling reject_comments, which handles other people's comments on your videos. An agent can differentiate it from edit_comment, list_comments, and reject_comments without opening any schema.

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?

Explicitly names the alternative path: others' comments 'can't be deleted, only rejected, which hides them,' routing the agent to reject_comments. It also states the precondition for the call ('Without confirm, nothing is deleted') and what happens if it is omitted, so an agent knows exactly when this tool is and is not the right choice.

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