Google Play Console MCP

Overview Schema Source Related Servers Discussions Admin

Batch Update Subscription Offer States

batch_update_subscription_offer_states

Update states of multiple subscription offers in a single API call. Provide package name, product ID, base plan, and list of activation/deactivation requests.

Instructions

Activate or deactivate multiple subscription offers in a single operation.

Disabled in read-only mode.

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>",
      "product_id": "<product_id>",
      "base_plan_id": "<base_plan_id>",
      "requests": "<requests>"
    },
    "name": "batch_update_subscription_offer_states"
  }
}

Input Schema

Name	Required	Description
`requests`	Yes	List of UpdateSubscriptionOfferStateRequest bodies (each with a nested activateSubscriptionOfferRequest or deactivateSubscriptionOfferRequest)
`product_id`	Yes	Parent subscription product ID
`base_plan_id`	Yes	Parent base plan ID ('-' wildcard allowed)
`package_name`	Yes	App package name

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description clearly states the mutation behavior — activating or deactivating offer states — and adds the operational restriction 'Disabled in read-only mode,' which is useful since no annotations are provided. However, it does not disclose partial-failure behavior, reversibility, permission requirements, or whether the batch is atomic, which matters for a state-changing batch 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?

The description is two short sentences with no filler: the core operation is front-loaded, and the read-only restriction is stated separately. Every sentence earns its place.

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?

The schema provides full parameter documentation and an output schema exists, so the description does not need to explain return values. Still, for a batch mutation tool, the absence of guidance about when to use this over the single-offer siblings and the lack of batch-failure semantics leave the description only minimally 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 100%, with each parameter already documented, including the nested request structure. The description adds no new parameter-level meaning beyond restating the activate/deactivate intent, so the baseline of 3 is appropriate.

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 opens with a specific verb phrase, 'Activate or deactivate multiple subscription offers,' naming both the action and the resource with a clear batching scope. This effectively distinguishes it from single-offer sibling tools like activate_subscription_offer and deactivate_subscription_offer, even without naming them.

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 'in a single operation' implies the batching use case, and the operation type is clear. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of single-offer alternatives or conditions that would favor activate_subscription_offer instead.

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

Deploy Server