Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Batch Delete One Time Products

batch_delete_one_time_products

Delete multiple one-time products from your Google Play app in a single operation. Provide the package name and a list of delete requests to remove them.

Instructions

Delete multiple one-time products in a single operation.

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

Input Schema

NameRequiredDescriptionDefault
requestsYesList of DeleteOneTimeProductRequest bodies (each with productId and optional packageName / latencyTolerance)
package_nameYesApp package name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds 'Disabled in read-only mode,' which is useful and signals mutation. However, it does not disclose partial-failure behavior, irreversibility, or side effects beyond deletion, so it provides moderate but incomplete transparency.

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?

The description is two short sentences: the first states the core operation, the second notes the read-only restriction. Every word earns its place, and there is no extraneous information.

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 two-parameter tool with full schema coverage and an output schema, the description covers the essential purpose and the read-only restriction. It is complete enough for an agent to invoke the tool, though it could add explicit alternative routing or failure semantics.

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 schema already describes both parameters fully, with requests documented as 'List of DeleteOneTimeProductRequest bodies' and package_name as 'App package name.' At 100% schema coverage, the description adds no additional parameter meaning, matching the baseline of 3.

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 ('multiple one-time products'), and the batching scope ('in a single operation'). This distinguishes it from the single delete_one_time_product and batch_delete_in_app_products siblings.

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 phrase 'multiple one-time products in a single operation' clearly implies when to use this tool: when deleting several one-time products at once rather than calling the single-delete tool repeatedly. It does not explicitly name alternatives or exclusions, 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

Other Tools