Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_delete_comment

Destructive

Reads and previews deletion of an immutable creator-channel comment using a comment ID from channel threads or moderation lists.

Instructions

Read and preview deletion of an immutable creator-channel comment.

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": {
      "commentId": "<commentId>"
    },
    "name": "youtube_preflight_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentIdYesID of a comment on the selected channel, from youtube_list_channel_comment_threads or youtube_list_moderation_comments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / commentId / description
      Added value: +"ID of a comment on the selected channel, from youtube_list_channel_comment_threads or youtube_list_moderation_comments."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

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

The annotation declares destructiveHint=true, but the description frames the tool as 'Read and preview deletion', which suggests a read-only dry run. It does not clarify whether any state changes, confirmation tokens, or irreversible effects occur, creating a contradiction with the annotation.

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 a single front-loaded sentence with no wasted text. It is appropriately sized for the tool's apparent scope.

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?

For a preflight deletion tool with no output schema, the description does not explain what the preview returns, whether a follow-up confirmation is needed, or how it relates to youtube_delete_comment. The single sentence is too sparse for safe invocation.

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?

The only parameter, commentId, is fully documented in the schema at 100% coverage, including where to obtain it. The description adds no additional parameter meaning, so the baseline of 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?

The description states a specific verb and resource: reading and previewing deletion of a creator-channel comment. It implicitly distinguishes itself from the actual delete sibling via 'preview', but does not name the alternative or define scope more explicitly.

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?

'Preview deletion' implies this should be used before deleting a comment, especially given the sibling youtube_delete_comment. However, the description does not explicitly say when to use it, when not to use it, or what prerequisites are required.

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