Google Play Console MCP

by abd3lraouf-studios

Overview Schema Source Related Servers Discussions Admin

Python

Local

Acknowledge Product Purchase

acknowledge_product_purchase

Acknowledge in-app product purchases before the 3-day deadline to avoid automatic refunds.

Instructions

Acknowledge an in-app product purchase.

Purchases not acknowledged within 3 days are automatically refunded.

Input Schema

TableJSON Schema

Name	Required	Description
`product_id`	Yes	In-app product SKU
`package_name`	Yes	App package name
`purchase_token`	Yes	The purchase token from the client app
`developer_payload`	No	Optional payload to associate with the purchase

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It discloses an important consequence (automatic refund after 3 days if unacknowledged), but does not mention idempotency, side effects, authorization requirements, or what happens after a successful acknowledgment.

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 two short sentences with no filler. The core action is front-loaded, and the critical policy detail is stated concisely immediately after.

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 description covers the main purpose and a key consequence, and the output schema exists so return values need not be described. However, with no annotations and no mention of how this differs from consume_product_purchase or when acknowledgment is optional, it is only minimally complete for correct selection and invocation.

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%, so the input schema fully documents all parameters. The description adds no additional parameter-level meaning, which matches the baseline of 3 for high schema coverage.

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 clearly states the action (acknowledge) and the resource (an in-app product purchase). It is clear and specific, though it does not explicitly distinguish itself from sibling tools like consume_product_purchase or acknowledge_subscription_purchase.

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

Usage Guidelines3/5

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

The description implies when to use the tool: purchases should be acknowledged promptly, and failing to do so within 3 days results in automatic refunds. However, it does not explicitly mention alternatives or exclusions, such as using consume_product_purchase for consumable items or acknowledge_subscription_purchase for subscriptions.

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

Deploy Server