Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_set_comment_moderation_status

Destructive

Preview a YouTube comment moderation status change—heldForReview, published, or rejected—before applying it; banning the author requires prior review and elevated: true.

Instructions

Read and preview a comment moderation action; banning requires elevated intent.

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>",
      "moderationStatus": "<moderationStatus>"
    },
    "name": "youtube_preflight_set_comment_moderation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
elevatedNoMust be true when banAuthor is true, after the user reviewed the ban.
banAuthorNoAlso ban the comment author; allowed only with rejected and needs elevated: true.
commentIdYesID of a comment on the selected channel, from youtube_list_channel_comment_threads or youtube_list_moderation_comments.
moderationStatusYesNew moderation status: heldForReview, published or rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • addedInput schema / properties / banAuthor / description
      Added value: +"Also ban the comment author; allowed only with rejected and needs elevated: true."
    • 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 / elevated / description
      Added value: +"Must be true when banAuthor is true, after the user reviewed the ban."
    • addedInput schema / properties / moderationStatus / description
      Added value: +"New moderation status: heldForReview, published or rejected."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotation destructiveHint=true would otherwise read as a mutating tool, and 'read and preview' usefully clarifies that this is a dry-run preview of a destructive action plus the elevated-intent condition for banning. It stops short of explaining what the preview returns or confirming no state change occurs.

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 wasted words. The preview purpose comes first, followed by the elevated-intent caveat.

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?

For a 4-param preflight of a destructive action with no output schema and full schema coverage, the description is minimally adequate. It omits what the preview yields and how it links to the real setter, which an agent would need to chain correctly.

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 description coverage is 100%, so the schema already documents commentId, moderationStatus, banAuthor, and elevated thoroughly. The description's 'banning requires elevated intent' lightly reinforces the elevated/banAuthor relationship but adds little beyond the schema — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Read and preview a comment moderation action,' which conveys the preview/dry-run nature despite the tool name containing 'set'. However, it never explicitly states that it does not perform the mutation or that youtube_set_comment_moderation_status is the executor, so the verb-vs-name tension leaves purpose only partially resolved.

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

Usage Guidelines2/5

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

'Banning requires elevated intent' is a precondition, not usage routing. There is no explicit statement of when to use this versus the actual youtube_set_comment_moderation_status tool, and no 'when-not' guidance.

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