Google Play MCP

deactivate_base_plan

Deactivate a subscription base plan to stop new purchases while existing subscribers continue renewing. Use it to retire or pause a plan without disrupting current subscribers.

Instructions

Deactivate a base plan: no NEW purchases (existing subscribers keep renewing). Gated by PLAY_MCP_ALLOW_SUBSCRIPTION_ACTIVATION.

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>",
      "basePlanId": "<basePlanId>"
    },
    "name": "deactivate_base_plan"
  }
}

Input Schema

Name	Required	Description
`productId`	Yes	Subscription product id
`basePlanId`	Yes
`packageName`	Yes	Application id (package name), e.g. com.example.app
`latencyTolerance`	No	Optional propagation latency tolerance (default latency-sensitive)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations supplied, the description carries the burden and does real work: it explains the differential effect on existing subscribers versus new purchases and names the feature flag that can block the call. It stops short of saying whether the change is reversible (activate_base_plan exists) or whether it is staged in an edit requiring commit_edit.

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, zero filler, and the most decision-relevant fact (existing subscribers keep renewing) is placed up front rather than buried.

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 an unannotated mutation tool with no output schema, the definition covers effect and gating but omits the workflow context that matters in this API family, namely whether the change is staged in an edit and requires commit_edit, plus whether it can be undone. It is adequate rather than complete.

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 75%, near the high-coverage threshold, and the description adds nothing about parameters. basePlanId in particular has no description anywhere, and the latencyTolerance default is only documented in the schema.

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?

States a specific verb and resource (deactivate a base plan) and immediately defines what that means operationally: no new purchases while existing subscribers keep renewing. That parenthetical is what separates this from delete_base_plan, so an agent can pick the right tool without opening the schema.

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 gating variable PLAY_MCP_ALLOW_SUBSCRIPTION_ACTIVATION is disclosed, which is genuine prerequisite guidance. However, there is no routing advice between this and delete_base_plan or deactivate_subscription_offer, so the choice of tool is left implicit.

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

Deploy Server