google-play-developer-mcp

purchases_subscriptions_v2_defer

Defer subscription billing by specifying expected and desired expiry times to delay the renewal.

Instructions

Defer billing for a subscription (2026-01 supports subscriptions with add-ons too). Pass DeferralInfo with expectedExpiryTime + desiredExpiryTime.

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>",
      "deferralInfo": "<deferralInfo>"
    },
    "name": "purchases_subscriptions_v2_defer"
  }
}

Input Schema

Name	Required	Description
`token`	Yes	Purchase token returned by the Play Billing library
`packageName`	Yes	Android application package name, e.g. com.example.app
`deferralInfo`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided. The description adds that it supports add-ons (version 2026-01) and mentions required fields, but fails to disclose behavioral traits like authorization needs, effect on billing, or error conditions.

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 sentences: first states purpose and key feature, second explains required input. No redundant words, front-loaded, efficient.

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?

Given the presence of a nested object (deferralInfo) and no output schema or annotations, the description covers the input structure well but lacks information about response, prerequisites, or side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% (packageName and token have descriptions, deferralInfo lacks). The description adds meaning by specifying that deferralInfo requires expectedExpiryTime and desiredExpiryTime, compensating for the schema gap.

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 'Defer billing for a subscription' with a specific verb and resource, and distinguishes from siblings like cancel, revoke, acknowledge by mentioning 'supports subscriptions with add-ons too'.

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 usage via 'Defer billing' and tells what to pass, but does not explicitly state when to defer vs. alternative subscription operations (acknowledge, cancel, revoke) nor when not to use.

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

Deploy Server