app-publish-mcp

google_list_iap

List all in-app products for a Google Play app by package name, with pagination support, so you can review managed products before updating or managing them.

Instructions

List all in-app products (managed products) for an app

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": "google_list_iap"
  }
}

Input Schema

Name	Required	Description	Default
`pageToken`	No	Pagination token from the previous response
`packageName`	Yes	Android package name

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 25, 2026

addedInput schema / properties / pageToken

Added value: +{
+  "description": "Pagination token from the previous response",
+  "type": "string"
+}

First observedv0.3.1Mar 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only operation, how pagination works, authentication requirements, or what the response contains, even though the pageToken parameter signals pagination.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately sized for a simple list operation.

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?

For a simple two-parameter list tool with complete schema descriptions, the core purpose is covered. However, without annotations or an output schema, the description could usefully mention pagination behavior or the shape of the returned list, so it is only minimally complete.

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 both parameters are fully documented in the schema. The description adds no extra meaning for packageName or pageToken beyond what the schema already provides, which is the expected baseline when schema coverage is high.

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 clear verb ('List') and resource ('in-app products (managed products)') scoped to an app. It distinguishes the resource from subscriptions, but does not explicitly contrast with sibling list tools such as google_list_one_time_products or google_list_subscriptions.

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?

Provides no explicit guidance on when to use this tool versus the sibling google_get_iap, google_list_one_time_products, or google_list_subscriptions. The listing intent is implied, but no exclusions or alternatives are named.

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

Deploy Server