Google Play MCP

update_inapp_product

Patch specific in-app product fields like status, listings, or prices; use dry-run to preview before/after diffs before immediate changes.

Instructions

Patch an in-app product: only the fields in product change (status, listings, defaultPrice, prices, ...). Changing defaultPrice/prices is a PRICE CHANGE and is gated by PLAY_MCP_ALLOW_PRICE_CHANGES. Set dryRun:true to see the before/after diff without writing. Takes effect immediately (no edit).

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

Input Schema

Name	Required	Description
`sku`	Yes
`dryRun`	No	Preview the diff without writing (default false)
`product`	Yes	Partial InAppProduct
`packageName`	Yes	Application id (package name), e.g. com.example.app
`latencyTolerance`	No	Optional propagation latency tolerance (default latency-sensitive)
`autoConvertMissingPrices`	No	Re-derive regional prices from defaultPrice (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses partial-patch semantics (unlisted fields untouched), an environment-variable permission gate for price mutations, a non-destructive preview mode, and that changes apply immediately rather than requiring a separate edit commit. These are exactly the behavioral traits an agent needs before calling a mutation.

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?

Four short sentences, front-loaded with the patch scope, then the risk gate, then the preview escape hatch, then the timing caveat. Capitalized PRICE CHANGE draws the eye to the consequential behavior; nothing is redundant with the schema.

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 six-parameter mutation with a nested object, no annotations, and no output schema, the description covers the critical risks (price gating, immediacy, partial update) and the preview path. It does not describe what a failed gated call returns or how latencyTolerance affects propagation, leaving minor gaps.

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

Parameters4/5

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

Schema coverage is 83%, so the schema already documents most parameters. The description still adds real meaning beyond it by enumerating patchable fields (status, listings, defaultPrice, prices) and by flagging that defaultPrice/prices are a gated PRICE CHANGE; latencyTolerance and autoConvertMissingPrices are left to their schema text.

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?

Uses a specific verb ("Patch") plus resource (in-app product) and states the precise scope: "only the fields in `product` change". The clause "Takes effect immediately (no edit)" separates it from the edit-based workflow tools (commit_edit/delete_edit) and from create/delete siblings without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete conditions for the two usage decisions that matter: set dryRun:true to preview, and note that price fields are gated by PLAY_MCP_ALLOW_PRICE_CHANGES. It does not explicitly say when to prefer this over create_inapp_product or update_listing, so it lacks named alternatives, but the context is clear.

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

Deploy Server