Google Play Console MCP

Overview Schema Source Related Servers Discussions Admin

Delete One Time Product

delete_one_time_product

Deletes a one-time product from the Google Play catalog. Specify the app package name and product ID to remove it permanently.

Instructions

Delete a one-time product from the catalog.

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

Input Schema

Name	Required	Description	Default
`product_id`	Yes	One-time product ID
`package_name`	Yes	App package name

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

There are no annotations, and the description only says 'Delete' and mentions read-only mode. It does not disclose whether deletion is permanent, whether associated data is affected, what authorization is required, or what side effects follow. For a destructive operation, this is a significant transparency gap.

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 short, purposeful sentences with no filler. The core operation is front-loaded, and the read-only-mode warning is a meaningful addition that earns its place.

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 destructive tool, the description is minimally adequate but leaves gaps: it omits irreversible-deletion consequences, prerequisites or side effects, and does not route the agent away from sibling delete tools. The output schema covers return shape, so that part is not an issue.

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?

The input schema provides descriptions for both parameters, giving 100% schema coverage. The description adds no parameter-specific meaning, but the baseline of 3 applies because the schema already documents product_id and package_name adequately.

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 states a specific verb ('Delete'), a clear resource ('one-time product'), and a location ('catalog'). This is unambiguous and distinguishes the tool from sibling delete operations like delete_in_app_product or delete_subscription at the resource-type level.

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?

The description provides one useful exclusion ('Disabled in read-only mode'), but it does not explicitly say when to use this tool versus alternatives such as delete_in_app_product or delete_subscription. The intended usage is mostly inferred from the tool name and the one-time-product resource.

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

Deploy Server