Google Play Console MCP

Overview Schema Source Related Servers Discussions Admin

Patch One Time Product

patch_one_time_product

Create or update a one-time product in Google Play Console by specifying fields to change and an update mask. Use for adding or modifying in-app products.

Instructions

Create or update a one-time product (patch is create-or-update).

Disabled in read-only mode.

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": {
      "package_name": "<package_name>",
      "product_id": "<product_id>",
      "product": "<product>",
      "update_mask": "<update_mask>"
    },
    "name": "patch_one_time_product"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes	Partial OneTimeProduct resource body with fields to change
`product_id`	Yes	One-time product ID
`update_mask`	Yes	Comma-separated list of fields to update
`package_name`	Yes	App package name
`regions_version`	No	Version of available regions for regional prices (default: "2022/02")	2022/02

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

A4/5.0

Behavior3/5

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

The description discloses that the tool mutates state and is disabled in read-only mode, which is useful given no annotations. However, it does not detail other behavioral aspects such as partial-update mechanics, idempotency beyond 'create-or-update', or permission requirements.

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 concise sentences with no redundancy. The core purpose is stated first, followed by a useful operational constraint. Every sentence earns its place.

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 mutating tool with 5 parameters, 100% schema coverage, an output schema, and no annotations, the description provides the essential extras: upsert behavior and read-only-mode restriction. It relies on the schema for parameter details, which is appropriate.

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 the baseline is 3. The description itself adds no parameter-specific meaning, but the input schema already documents each parameter, including the update_mask and partial product body, so the agent is not left without guidance.

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 clearly states a specific verb ('Create or update') and a specific resource ('one-time product'), and clarifies the PATCH semantics as create-or-update. This distinguishes it from batch operations and other patch tools without requiring the agent to infer intent from the name alone.

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?

The description gives clear context: use this tool to create or update a single one-time product. It implies the comparison to batch-oriented siblings like batch_update_one_time_products and single-resource tools, though it does not explicitly name alternatives or state when not to use it.

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

Deploy Server