Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete Review Reply

delete_review_reply

Retract a developer reply to a Google Play review by replying with empty text, clearing the visible reply since no delete endpoint exists.

Instructions

Retract a developer reply to a review.

The Play API has no delete-reply endpoint. The reply is retracted by replying again with empty text, which clears the visible reply; the result records the mechanism so this is not mistaken for erasure from history.

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": {
      "package_name": "<package_name>",
      "review_id": "<review_id>"
    },
    "name": "delete_review_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
review_idYesReview whose reply should be retracted
package_nameYesApp package name (e.g., com.example.myapp)
confirmation_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior5/5

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

No annotations are provided, so the description must carry the behavioral burden, and it does. It explains that the reply is actually retracted by replying again with empty text, that this clears only the visible reply, and that the result records the mechanism to avoid confusion with history erasure. This is detailed, honest disclosure of what the operation really does.

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?

The description is three sentences that front-load the purpose and add only necessary nuance. Every sentence provides distinct information: what it does, why the mechanism is indirect, and the record-keeping caveat. No redundancy.

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?

The behavioral mechanism is covered well, and an output schema exists, so return values are presumably documented. However, two optional parameters are left unexplained and the absence of annotations means the agent has no safety clues. Overall it is functional but with meaningful gaps.

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?

Only review_id and package_name have schema descriptions; confirm and confirmation_token are undocumented. The description mentions the retraction mechanism but does not explain how those two optional parameters work or whether they must be set. At 50% schema coverage, the description should have compensated but does not.

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?

The description opens with a clear verb and object: 'Retract a developer reply to a review.' It further clarifies the nature of the operation by noting the Play API lacks a delete endpoint and the retraction is achieved via replying with empty text. This distinguishes it from a true delete, though it does not explicitly contrast with sibling tools like reply_to_review.

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 does not state when to choose this tool over alternatives, nor does it mention reply_to_review or any other sibling. The implied usage is limited to the opening imperative 'Retract a developer reply to a review,' with no exclusion conditions or alternative references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools