Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_delete_comment

Destructive

Deletes an approved creator-channel comment only after explicit approval, using the comment ID and approval ID to confirm removal.

Instructions

Delete an approved 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>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
commentIdYesID of a comment on the selected channel, from youtube_list_channel_comment_threads or youtube_list_moderation_comments.
approvalIdYesApproval ID from the youtube_preflight_delete_comment preview, after approving it with youtube_approve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_delete_comment preview, after approving it with youtube_approve."
    • 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."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds the approval prerequisite and channel scope, but 'immutable' is ambiguous and it never plainly states that the deletion is permanent/irreversible or what permissions are needed — context that would matter for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. Slight deduction because 'immutable' is ambiguous and may cost more in reader confusion than it earns.

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

Completeness3/5

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

No output schema is needed, and the schema descriptions cover the approval workflow and parameter sources. However, for a destructive, irreversible action the description is thin: it should state permanence and any auth/scope preconditions rather than relying entirely on the schema.

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?

Schema coverage is 100%, so commentId, approvalId and confirm are fully documented in the schema, including source tools and the approval flow. The description adds nothing about parameters, so the baseline 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?

States a specific verb (delete) and resource (comment) scoped to 'approved immutable creator-channel' comments, making it distinguishable from general comment tools. It does not explicitly name the preflight sibling, but the word 'approved' points to the workflow it completes.

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?

Usage is only implied: 'approved' signals that youtube_preflight_delete_comment plus youtube_approve must precede it, and those steps are spelled out in the schema's parameter descriptions rather than in the description. There is no explicit when-to-use/when-not or alternative routing in the description itself.

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