Google Play Console MCP

Overview Schema Source Related Servers Discussions Admin

List Purchase Option Offers

list_purchase_option_offers

List offers associated with a one-time product purchase option. Supply package name, product ID, and purchase option ID to retrieve all available offers for review and management.

Instructions

List all offers for a one-time product purchase option.

Input Schema

TableJSON Schema

Name	Required	Description
`product_id`	Yes	Parent one-time product ID ('-' wildcard lists across products)
`package_name`	Yes	App package name
`purchase_option_id`	Yes	Parent purchase option ID ('-' wildcard lists across options)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It indicates a read-only listing operation, but it does not mention pagination, return-value shape, or edge cases related to the '-' wildcards beyond what the schema already states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler words. It is concise, though slightly too terse to carry the behavioral and usage context that would make it more useful.

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?

With no output schema and no annotations, the description leaves out return-value expectations and how to differentiate this tool from batch_get_purchase_option_offers. The schema covers parameters well, but the overall context is incomplete for an agent deciding whether to invoke this tool.

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 all parameters are already documented, including wildcard behavior. The description adds no new parameter-level meaning, which matches the baseline for fully covered schemas.

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 clear verb and resource: it lists offers for a one-time product purchase option. However, it does not explicitly distinguish this from the similar sibling tool batch_get_purchase_option_offers, so it stops short of a 5.

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 batch_get_purchase_option_offers or the purchase option offer state-management tools. The word 'all' hints at bulk listing, but no explicit context, exclusions, or alternatives are provided.

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

Deploy Server