google-play-developer-mcp

orders_review_refund

Respond to a pending chargeback refund review within 24 hours of a PendingRefundReviewNotification. Submit a refund preference and usage evidence so Google Play can dispute the chargeback.

Instructions

Respond to a pending refund review (collaborative chargeback, 2026-07). Call within 24 hours of a PendingRefundReviewNotification. Supply refundPreference and optional usage evidence so Play can dispute the chargeback.

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": {
      "packageName": "<packageName>",
      "orderId": "<orderId>",
      "pendingRefundToken": "<pendingRefundToken>",
      "refundPreference": "<refundPreference>",
      "sampleContentProvided": "<sampleContentProvided>"
    },
    "name": "orders_review_refund"
  }
}

Input Schema

Name	Required	Description
`orderId`	Yes
`packageName`	Yes	Android application package name, e.g. com.example.app
`refundPreference`	Yes	Whether Play should grant the refund
`pendingRefundToken`	Yes	Token from the PendingRefundReviewNotification
`sampleContentProvided`	Yes	Whether a free sample, trial, or functionality preview was offered before purchase
`consumptionUsageEvents`	No
`consumptionPercentageMilliunits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Oct 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the 24-hour window and the outcome ('so Play can dispute the chargeback'), which is useful, but says nothing about required permissions, reversibility, what APPROVE vs DECLINE vs NEUTRAL actually causes, or rate limits.

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?

Three short sentences, front-loaded with the purpose and then the timing constraint. Efficient overall, though the parenthetical 'collaborative chargeback, 2026-07' is cryptic and consumes space without clarifying behavior.

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 7-param mutation with no annotations and no output schema, the description covers the trigger and intent but omits auth requirements, the effect of each refundPreference value, and the response. Adequate but with visible 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 coverage is only 57%. The description names refundPreference and gestures at the optional usage-evidence params, adding some intent beyond the schema, but it leaves orderId and the consumption* params unexplained and adds no syntax detail for the ones it does mention.

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+resource: 'Respond to a pending refund review' with the qualifier 'collaborative chargeback'. This is distinguishable from the sibling orders_refund, though the description never names that sibling to make the routing explicit.

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 a clear trigger and timing constraint: 'Call within 24 hours of a PendingRefundReviewNotification'. That is actionable context, but there is no explicit when-not or named alternative (e.g. orders_refund for a direct refund), so it stops short of full routing guidance.

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

Deploy Server