Skip to main content
Glama

Business Profile: Reply review

gbp_reply_review

Post the owner's public reply to a review. Runs as a preview unless confirm is true; the reply text is published under the business name, so show it to the person 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": {
      "gbp_location_id": "<gbp_location_id>",
      "review_id": "<review_id>",
      "comment": "<comment>"
    },
    "name": "gbp_reply_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYes
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
review_idYesFrom gbp_reviews
gbp_location_idYesFrom gbp_list_locations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Leave false to preview. Set true only after the user has approved this exact text."New value: +"Leave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations establish write/openWorld/non-idempotent, and the description adds context beyond them: the two-phase preview-then-confirm flow and, critically, that the text is published publicly under the business name. That public-visibility consequence is the key behavioral fact an agent must convey before acting.

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 tight sentences, front-loaded with the action, followed by the safety-critical preview and visibility caveats. No wasted words.

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 non-idempotent write tool with no output schema, the description covers the mutation semantics, preview gate, and public consequence, and annotations cover safety posture. It does not describe the post-success result, but that is a minor gap here.

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 75%; confirm, review_id, and gbp_location_id are documented in the schema. The description reinforces the confirm preview/confirm semantics and clarifies that comment is public reply text, compensating for the undocumented comment field, though it doesn't restate its length bound.

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 the owner's public reply to a review.' This is clearly distinct from the closest sibling, gbp_reviews (which reads reviews), so an agent can pick the right tool 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 Guidelines4/5

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

Gives clear operational guidance: it runs as a preview unless confirm is true, and advises showing the reply to the person first. It stops short of naming alternatives or explicit when-not-to-use conditions, which keeps it from 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.