Google Play MCP

get_subscription_offer

Read a single subscription offer to retrieve its phases, regional prices, eligibility, and state for auditing, support checks, or verifying details before updates.

Instructions

Read one subscription offer (phases, regional prices, eligibility, state). Read-only.

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>",
      "offerId": "<offerId>"
    },
    "name": "get_subscription_offer"
  }
}

Input Schema

Name	Required	Description
`offerId`	Yes
`productId`	Yes	Subscription product id
`basePlanId`	Yes
`packageName`	Yes	Application id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does assert 'Read-only' and identifies the categories of data returned, which is useful behavioral context, but it says nothing about required permissions, behavior when the offer is absent, or edit/draft visibility.

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?

Two compact sentences with the read scope front-loaded and the 'Read-only' qualifier appended. No filler, though the telegraphic field list reads more like a schema echo than a structured explanation.

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?

Four required parameters with half undocumented, no output schema, and no annotations make this a moderately complex tool whose description is thin. It compensates slightly by naming the returned data categories, but identifier semantics and failure behavior remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: productId and packageName are documented in the schema, while offerId and basePlanId are bare strings in both the schema and the description. The description adds no meaning about the identifier hierarchy (packageName > productId > basePlanId > offerId) or value formats, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Read one subscription offer') and enumerates what the read covers: phases, regional prices, eligibility, state. The word 'one' distinguishes it from list_subscription_offers, but it does not name any sibling explicitly, so differentiation is inferred rather than stated.

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?

Usage is only implied by the phrase 'Read one', which suggests single-offer retrieval versus a list call or a mutation. There is no explicit when-to-use, no prerequisites (edit context, permissions), and no named alternative.

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

Deploy Server