Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Batch Update Purchase Option Offers

batch_update_purchase_option_offers

Batch update or create multiple one-time product offers with a single API call. Provide package name, product ID, purchase option ID, and request bodies to apply changes.

Instructions

Create or update multiple one-time product 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>",
      "purchase_option_id": "<purchase_option_id>",
      "requests": "<requests>"
    },
    "name": "batch_update_purchase_option_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsYesList of UpdateOneTimeProductOfferRequest bodies (each with oneTimeProductOffer, updateMask, and optional allowMissing / latencyTolerance)
product_idYesParent one-time product ID ('-' wildcard allowed)
package_nameYesApp package name
purchase_option_idYesParent purchase option ID ('-' wildcard allowed)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately indicates a write/mutation operation and a read-only-mode restriction, but it does not disclose batch semantics such as partial failure behavior, atomicity, idempotency, or what happens when wildcard IDs resolve to multiple parents.

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 primary capability is front-loaded, and the read-only-mode warning is the only additional sentence, both earning their 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 description is minimally viable: it identifies the operation, resource, and batch nature, and the output schema exists to explain return values. However, given the large sibling list and the absence of annotations, the definition would benefit from clarifying when this batch offer operation should be chosen over similar batch tools, and from noting behavioral aspects like partial failure or wildcard handling.

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, including wildcard behavior and the structure of requests. The description adds no parameter-level meaning beyond the schema, which matches the baseline expectation.

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 states a specific operation ('Create or update multiple one-time product offers') and clearly identifies the resource type (purchase option offers). It distinguishes itself from similar batch tools like batch_update_one_time_products and batch_update_subscription_offer_states by explicitly naming one-time product offers.

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 provides no guidance on when to use this tool versus alternatives such as batch_update_one_time_products, batch_update_purchase_option_offer_states, or single-offer operations. The only usage-related note, 'Disabled in read-only mode,' is a constraint, not a selection criterion.

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