Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Batch Update Subscription Offers

batch_update_subscription_offers

Update multiple subscription offers in a single operation by specifying package name, product ID, base plan ID, and a list of update requests.

Instructions

Update 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_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsYesList of UpdateSubscriptionOfferRequest bodies (each with subscriptionOffer, updateMask, and optional regionsVersion)
product_idYesParent subscription product ID
base_plan_idYesParent base plan ID ('-' wildcard allowed)
package_nameYesApp package name

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the behavioral disclosure burden, but it only adds 'Disabled in read-only mode.' This signals a mutating operation and an environment restriction, yet it does not explain partial-failure behavior, whether this is a full overwrite or patch, or what auth/editing context is required.

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 extremely concise and front-loaded: the first sentence captures the core purpose, and the second adds a useful mode restriction. No sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite good schema coverage and an output schema, the description is not complete enough for selection among many batch/update siblings. It lacks usage criteria, mutation semantics, and behavior on partial failures, which are important for a batch write with no annotations.

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 baseline is 3. The description adds no parameter detail beyond the schema, but the schema already documents package_name, product_id, base_plan_id, and requests, including the updateMask and regionsVersion contents.

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 states a concrete action — updating multiple subscription offers in one operation — with a clear verb and resource. However, it does not explicitly differentiate this from sibling tools like batch_update_subscription_offer_states or patch_subscription_offer, so it misses the highest level of purpose clarity.

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?

There is no guidance about when to use this tool instead of the single-offer update or state-update siblings. The phrase 'in a single operation' only implies batching; it does not state preconditions, exclusions, or alternatives.

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