Skip to main content
Glama
Sign In
google-play-developer-mcp

google-play-developer-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

purchases_subscriptions_acknowledge

Acknowledge a Google Play subscription purchase with its token to confirm fulfillment and prevent automatic refund or revocation.

Instructions

Acknowledge a subscription purchase. 2025-11+ accepts optional externalAccountId for account-linking. (v1 endpoint retained for compatibility.)

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>",
      "token": "<token>"
    },
    "name": "purchases_subscriptions_acknowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesPurchase token returned by the Play Billing library
packageNameYesAndroid application package name, e.g. com.example.app
subscriptionIdNo
developerPayloadNo
externalAccountIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states the basic action and notes about optional parameter and version compatibility, but does not disclose effects (e.g., idempotency, required permissions, post-acknowledgment behavior).

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?

Extremely concise: two sentences with no fluff. Every sentence adds value (purpose + version note). Front-loaded with the main action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema or annotations. The description lacks context on return values, error conditions, and the overall purchase flow (e.g., when to acknowledge). The compatibility note is helpful but insufficient for complete understanding.

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 low (40%), but the description adds meaning for 'externalAccountId' (account-linking since 2025-11). Other params (subscriptionId, developerPayload) remain undocumented in both schema and description. Partial improvement.

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?

The description clearly states 'Acknowledge a subscription purchase' with a specific verb and resource. This action is unique among sibling tools (no other acknowledge tool is listed), so it distinguishes well.

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?

No guidance on when to use this tool vs alternatives. The mention of 'v1 endpoint retained for compatibility' hints at a v2, but no explicit when-to-use or when-not-to-use instructions are provided.

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