Skip to main content
Glama

Reply to a YouTube comment

reply_to_youtube_comment

Post a public reply to a YouTube comment as the connected channel; it goes live right away. Get comment_id from list_youtube_comments. YouTube is in platform review: this only works for an account with a YouTube channel connected (list_accounts). Show the user the reply before posting it. Refused when the account holds agent posts for approval or the text has a blocked term.

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": {
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "reply_to_youtube_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reply, up to 10,000 characters.
accountNoOptional. Which connected YouTube channel replies (handle or id from list_accounts).
comment_idYesThe comment_id from list_youtube_comments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint=true, idempotentHint=false, destructiveHint=false), the description discloses that the reply is public and immediate, that the feature is gated by a platform review state, that human confirmation is required before posting, and that calls are refused under two specific conditions. This is meaningful operational context an agent cannot get from the structured fields.

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?

Four dense sentences, front-loaded with the action and immediacy before prerequisites and refusal conditions. Little waste, though the platform-review note could be folded more tightly into the precondition sentence.

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

Completeness4/5

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

For a 3-parameter, non-idempotent write tool with no output schema, the definition covers preconditions, workflow, and failure modes well. It does not say what a successful call returns (e.g., a new comment id), which is the only notable gap.

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% and the schema already documents text length, the optional account selector, and the comment_id source. The description's references to list_youtube_comments and list_accounts largely duplicate the schema text, adding no new format or constraint detail.

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 ("Post a public reply to a YouTube comment") plus the acting identity ("as the connected channel") and the immediacy of the effect. It is clearly distinguished from scheduling/queueing siblings by the "goes live right away" clause.

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 routes the agent to list_youtube_comments for comment_id and list_accounts for the channel, and states preconditions (account must have a connected YouTube channel). It also gives a mandatory workflow step (show the user the reply before posting) and two refusal conditions (account holds agent posts for approval, or text contains a blocked term).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources