Skip to main content
Glama

Social0

reply_to_comment

Destructive

Post a public reply to a comment on the originating network. Requires both comment_id and the publication_id from list_inbox_comments — Social0 verifies the comment is on that post before sending. This is a live public action; confirm the wording with the user first.

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

Input Schema

NameRequiredDescriptionDefault
textYesReply text
media_idNoMedia upload ID. Only X and Bluesky accept comment attachments.
comment_idYesComment ID from list_inbox_comments
publication_idYespublication_id from the same comment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and non-idempotent; the description adds valuable context beyond them by calling out that this is a live public action requiring user confirmation and that Social0 validates the comment belongs to that post before sending. It does not describe failure modes or duplicate-reply behavior for a non-idempotent write, leaving one gap.

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 tight sentences, front-loaded with the action, then prerequisites, then the safety caution. No filler or redundant restatement of the parameter names.

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 destructive, open-world write with no output schema, the description covers what it does, where the required inputs come from, and the confirmation protocol. It omits what a successful response contains and how platform-specific failures surface, which is a minor residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-tool provenance — that comment_id and publication_id must be sourced from list_inbox_comments and are cross-validated. That is real meaning not encoded in the schema. The `text` parameter gets no added guidance, keeping it below a 5.

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 ('Post a public reply') plus resource ('a comment') and scope ('on the originating network'), which cleanly separates it from reply_to_dm and moderate_comment. An agent knows exactly what action this performs without opening the schema.

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

Usage Guidelines4/5

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

Gives clear operational context: both IDs must come from list_inbox_comments, and the reply is a live public action that should be confirmed with the user first. It stops short of naming explicit alternatives (e.g., create_draft to stage wording) or when-not-to-use conditions, so it falls short of a 5.

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.