Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_reply_to_comment

Destructive

Posts a reply to an approved, immutable creator-channel comment using its comment ID, reply text, and approval ID from the required preflight approval.

Instructions

Reply to 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>",
      "text": "<text>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesReply text, up to 10000 characters.
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_reply_to_comment preview, after approving it with youtube_approve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_reply_to_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."
    • addedInput schema / properties / text / description
      Added value: +"Reply text, up to 10000 characters."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The destructiveHint annotation already flags this as a mutation. The description adds only that the comment must be approved and is 'immutable', but does not explain public visibility, reversibility, required permissions, or what the reply action affects.

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?

It is a single front-loaded sentence with no wasted words. The compression is slightly excessive because 'immutable creator-channel comment' is not self-explanatory.

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?

The rich schema covers the approval chain and parameter meanings, which helps an agent invoke the tool correctly. Still, for a destructive write operation with no output schema, the description does not explain the outcome of replying or how it relates to sibling comment tools.

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 all four parameters are fully documented in the schema. The description adds no parameter-level meaning beyond that baseline.

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 uses a specific verb ('Reply to') and resource ('comment'), and scopes it to approved creator-channel comments. It distinguishes replying from creating a top-level comment, though the phrase 'immutable creator-channel comment' is somewhat opaque.

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?

The word 'approved' implies a prerequisite approval flow, and the schema clarifies the preflight/approve chain via approvalId and confirm. However, the description itself does not explicitly say when to use this tool versus youtube_create_comment or youtube_preflight_reply_to_comment.

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