Google Play Console MCP

Overview Schema Source Related Servers Discussions Admin

Defer Subscription Purchase

defer_subscription_purchase

Defer a subscription purchase's next renewal date to a later time by specifying the desired duration and purchase details.

Instructions

Defer a subscription purchase's next renewal.

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>",
      "purchase_token": "<purchase_token>",
      "defer_duration": "<defer_duration>",
      "etag": "<etag>"
    },
    "name": "defer_subscription_purchase"
  }
}

Input Schema

Name	Required	Description
`etag`	Yes	Current etag of the subscription purchase
`package_name`	Yes	App package name
`defer_duration`	Yes	Duration to defer, e.g. "604800s" for 7 days
`purchase_token`	Yes	The purchase token from the client app

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior, but it only restates that a renewal is deferred. It does not explain that this mutates the subscription state, that the etag is needed for optimistic concurrency, whether the change is reversible, or what effect the deferral has on billing.

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 a single, tightly worded sentence with the verb and object front-loaded. There is no redundant phrasing or filler.

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 simple four-parameter action with full schema coverage and an output schema, the description is minimally adequate, but it leaves the lifecycle relationship to sibling tools implicit. An agent could invoke it, but not confidently distinguish when to defer versus cancel or revoke.

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 schema already documents all four parameters and their formats. The description adds little beyond naming the affected resource ('next renewal'), so it provides no significant meaning over the schema.

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 names a specific operation and resource: deferring the next renewal of a subscription purchase. It distinguishes 'defer' from sibling actions like cancel or revoke only by the verb and the 'next renewal' object, but does not explicitly compare them.

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 gives no instruction about when to choose this over cancel_subscription_purchase, revoke_subscription_purchase, or acknowledge_subscription_purchase, and no prerequisites are mentioned. The only usage signal is the purpose statement itself, which is tautological rather than guidance.

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

Deploy Server