Skip to main content
Glama

Reply to a comment

reply_to_comment

Post a reply to a comment on one of your posts. Creates the reply on the platform and records it in the inbox.

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_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reply text
comment_idYesThe comment id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the reply has a dual effect, written to the external platform and also recorded in the inbox. It stops short of mentioning permissions, rate limits, or failure behavior, which keeps it from a 5.

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?

Two short sentences with the action front-loaded and no filler. The second sentence partly restates the creation step but earns its place by disclosing the inbox side effect.

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?

For a two-parameter write tool with annotations present, the definition covers purpose and side effects adequately. However, with no output schema, it says nothing about what the call returns (e.g., a reply id or status), and it omits error or permission conditions, leaving modest gaps.

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% with only two parameters (comment_id, text) whose meanings are self-evident, so the schema does the heavy lifting. The description adds no constraints such as the 2000-character text limit or the source of comment_id, leaving it at 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?

States a specific verb and resource ('Post a reply to a comment on one of your posts') and clarifies that the reply is both created on the platform and recorded in the inbox. An agent can distinguish this from read-only siblings like list_comments, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The description implies when the tool applies but gives no explicit when-to-use versus alternatives, no prerequisites (e.g., needing a connected social account or a comment_id obtained from list_comments), and no exclusions. The agent must infer the full workflow context.

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