app-publish-mcp

google_update_iap

Update an existing in-app product's title, description, price, currency, or status for an Android app using its package name and SKU.

Instructions

Update an existing in-app product

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

Input Schema

Name	Required	Description
`sku`	Yes	Product SKU
`title`	No	Product title (for default language)
`status`	No
`description`	No	Product description (for default language)
`packageName`	Yes	Android package name
`defaultLanguage`	No	Default language
`defaultPriceMicros`	No	Price in micros
`defaultPriceCurrencyCode`	No	Currency code

Schema Changelog

Changes observed during successful MCP inspections.

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?

Without annotations, the description provides minimal behavioral context: it implies mutation but does not disclose whether updates are partial or full, required permissions, reversibility, or error conditions.

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, short sentence that efficiently conveys the core purpose without extraneous words. Could be slightly expanded for clarity without losing conciseness.

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?

Despite the presence of many sibling tools and 8 parameters, the description offers no differentiation from other update tools, no mention of return values, and no context for when to use 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?

With 88% schema description coverage, the schema already explains most parameters. The description adds no additional meaning beyond the schema, meeting the baseline.

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 'Update an existing in-app product' clearly states the action (update) and the resource (in-app product), distinguishing it from sibling tools like google_create_iap or google_delete_iap.

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?

Lacks guidance on when to use this tool versus alternatives (e.g., when to update vs create), and no mention of prerequisites or constraints.

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

Deploy Server