Skip to main content
Glama

reply_to_comment

Post a reply to one specific YouTube comment on the signed-in user's channel, on their behalf. ONLY call this after you have shown the user the exact reply text and they have explicitly approved posting it. It is a Klyf Pro feature and needs the user's one-time write permission; if they lack either, it returns the link they need. Use the comment's id from read_comments (the value after 'lc=' in that comment's reply link).

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>",
      "reply_text": "<reply_text>"
    },
    "name": "reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesThe id of the comment to reply to (the 'lc=' value from its reply link)
reply_textYesThe exact reply text the user approved

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds substantive behavior the annotations do not cover: an entitlement gate ('Klyf Pro feature'), a one-time write-permission requirement, and a graceful non-error fallback ('it returns the link they need') instead of a bare failure.

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?

Three sentences with no filler: purpose first, the mandatory approval gate second, the id source and entitlement caveat last. The most important constraint for a write tool is front-loaded rather than buried.

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 mutation tool with no output schema, it covers approval workflow, entitlement, and permission prerequisites well. The only soft spot is the vague phrase 'returns the link they need', which does not clarify whether that is an upgrade link, a consent link, or both.

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 both parameters are already documented in structured data, and the description's note about the 'lc=' value in the reply link largely restates the schema's own wording. The baseline of 3 applies because the schema carries the parameter burden.

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 reply to one specific YouTube comment') plus the acting identity ('on the signed-in user's channel, on their behalf'). This clearly separates it from read_comments, read_comment_thread, and enable_auto_reply, so an agent can pick it without opening a schema.

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?

Gives an explicit hard precondition ('ONLY call this after you have shown the user the exact reply text and they have explicitly approved posting it') and names the upstream tool that produces the id ('Use the comment's id from read_comments'). Both when-to-use and the exact alternative source are spelled out.

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