Google Play MCP

list_inapp_products

List managed one-time in-app products for an Android app, including SKU, status, listings, default price, and per-region prices, to review read-only product data.

Instructions

List managed (one-time) in-app products via the legacy inappproducts API: sku, status, listings, defaultPrice, per-region prices. Read-only. Subscriptions are under list_subscriptions.

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

Input Schema

Name	Required	Description	Default
`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

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden, and it partially meets it by declaring 'Read-only.' and listing the returned fields, which tells the agent what shape of data to expect. It says nothing about pagination, result caps, ordering, deprecated-API behavior, or auth requirements — real gaps for an unannotated tool.

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?

Two compact sentences, front-loaded with the action and API surface, then the returned fields, then the boundary condition. No filler or restatement of the tool name; every clause carries information.

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

Completeness4/5

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

For a single-parameter, read-only list tool with no output schema, the description supplies enough: what is listed, the API backing it, the fields returned, and where subscriptions live instead. The only meaningful omission is pagination/result-size behavior, which matters for catalog endpoints but is not fatal here.

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?

Only one parameter (packageName) and schema description coverage is 100%, with the schema already explaining the package-name format. The description adds no meaning beyond that — no mention of whether the package must be one the caller owns or how errors surface for an unknown package. Baseline 3 is appropriate.

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 — 'List managed (one-time) in-app products via the legacy inappproducts API' — and even enumerates the fields returned (sku, status, listings, defaultPrice, per-region prices). It explicitly carves out subscriptions, but does not distinguish itself from the sibling list_one_time_products, which is the most likely source of confusion given the 'one-time products' phrasing.

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?

Provides one explicit routing rule — 'Subscriptions are under list_subscriptions' — which is genuine when-not guidance. However, no guidance covers the legacy-vs-modern choice implied by the nearby list_one_time_products sibling, nor whether this is the preferred tool for a single app's catalog. Usage is implied rather than fully specified.

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

Deploy Server