Skip to main content
Glama

Reply to a review

reply_to_review
DestructiveIdempotent

Publishes a public reply to a review on its platform, through the platform’s official API, with exactly the text given. Where the platform allows editing it replaces an existing reply. Read-only platforms return reply_not_supported with the link to answer there.

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": {
      "review_id": "<review_id>",
      "text": "<text>"
    },
    "name": "reply_to_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reply, exactly as it will be published.
review_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the reply is public, that the text is published exactly as supplied, that an existing reply may be replaced where editing is allowed, and how unsupported platforms fail. These details meaningfully explain the destructive and open-world behavior implied by the annotations.

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?

Two sentences, front-loaded with the action and scope, followed by important edge behavior. There is no filler and every clause carries useful information.

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 two-parameter mutation with rich annotations, it covers the important behaviors: public visibility, exact text publishing, replacement semantics, and unsupported-platform errors. It is slightly incomplete about how review_id should be sourced and what authentication/connection requirements apply, but the core calling context is present.

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

Parameters2/5

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

Schema coverage is only 50%, and the description adds little parameter meaning: 'exactly the text given' largely duplicates the schema's text description, while review_id has no schema description and the tool description does not explain where to obtain it. The description does not compensate for the undocumented required parameter.

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?

It states a specific verb and resource: 'Publishes a public reply to a review on its platform.' This clearly distinguishes it from read-only siblings such as get_review and list_reviews while also clarifying that the reply is public and sent through the platform's official API.

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?

The description gives a clear usage context and one important exclusion: on read-only platforms it returns reply_not_supported with a link to answer there. It does not name sibling alternatives, but none of the listed siblings perform replies, so the remaining guidance is sufficient.

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