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

google-play-developer-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

purchases_products_consume

Consume a one-time product purchase so users can buy it again. This acknowledges the purchase and clears it for repurchase.

Instructions

Consume a consumable one-time product so the user can buy it again. Consuming also acknowledges the purchase.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesPurchase token returned by the Play Billing library
productIdYesProduct id / SKU — stable identifier you assign in Play Console
packageNameYesAndroid application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses a real side effect — that consuming also acknowledges the purchase — but omits prerequisites (purchase must be in the right state, only consumable products qualify), error behavior, and reversibility for what is clearly a mutating operation.

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 short sentences, front-loaded with the action and immediately followed by the user-visible consequence. No filler and nothing redundant with the schema.

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 3-required-parameter mutation tool with no annotations and no output schema, the description covers the core effect but leaves the agent without prerequisites, failure modes, or confirmation of what the call returns. Adequate but with clear 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 description coverage is 100%, with token, productId, and packageName all documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 (consume) and resource (consumable one-time product) and describes the resulting effect ('so the user can buy it again'). The added clause that consuming also acknowledges the purchase implicitly separates it from the sibling purchases_products_acknowledge, though no sibling is named explicitly.

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 phrase 'so the user can buy it again' implies when to use it (repeatable/consumable purchases), and the acknowledgement clause hints at the alternative path. However, there is no explicit when-not guidance or named alternative tool, so the agent must infer.

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