Skip to main content
Glama

Reply to a comment

reply_to_comment
Destructive

Publishes a reply, as the account, to a comment on a post Shager published (YouTube, Facebook Pages, Instagram, X, LinkedIn company Pages, Bluesky, Mastodon and Threads). It is public at once and can't be unsent, so a person approves each reply in Shager first: the first call answers needs_confirmation with confirm_url, where your human sees the comment and your exact text; after they approve, make the same call again and it goes out. Up to 2,200 characters, within the network's own limit (Bluesky 300, Threads 500, Mastodon the server's). On X the reply is billed to the workspace's monthly X limit. delete_comment can remove it again except on Threads. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>",
      "post_id": "<post_id>",
      "channel_id": "<channel_id>",
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
post_idYes
channel_idYes
comment_idYes
workspace_idYesWorkspace id from list_workspaces
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmation_token
      Added value: +{
      +  "description": "The confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructive/non-idempotent/openWorld annotations it discloses the concrete consequence (public at once, cannot be unsent), the human-approval gate and confirmation_token mechanics, per-network length ceilings (Bluesky 300, Threads 500, Mastodon server limit), and X billing against the workspace's monthly limit.

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?

The critical constraint (public, irreversible, requires approval) is front-loaded before limits and billing. It is dense but nearly every clause conveys operational facts; the parenthetical network list and billing aside add slight bulk.

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 6-parameter mutation tool with no output schema, it covers safety, approval flow, limits, billing, and reversal well. The remaining gap is the identity parameters, which an agent must infer from sibling listing 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 coverage is 33%, so the description must carry weight: it does explain the text limit and the confirmation_token/approval flow, but post_id, channel_id, and comment_id are left unexplained in both schema and description, and it never clarifies why channel_id is needed alongside post_id.

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?

"Publishes a reply, as the account, to a comment on a post Shager published" gives a specific verb, resource, actor, and scope, and enumerates the supported networks. It is clearly separable from siblings like delete_comment and hide_comment.

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?

It spells out the two-step usage path (first call returns needs_confirmation, human approves at confirm_url, then repeat the same call), names delete_comment as the reversal path with the Threads exception, and states it is unavailable in an unclaimed sandbox.

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