google-play-developer-mcp

onetime_products_batch_update

Update up to 100 one-time products in a single API call for your Android app.

Instructions

Update up to 100 one-time products in one call.

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

Input Schema

Name	Required	Description	Default
`requests`	Yes	Array of UpdateOneTimeProductRequest
`packageName`	Yes	Android application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It only mentions the batch size limit but does not disclose atomicity, partial failure behavior, permissions required, or return value. Minimal behavioral insight beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (10 words) and front-loaded, but too sparse. It omits important context that could fit in one or two more sentences without becoming verbose.

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?

For a batch update tool with no output schema and two required params, the description is incomplete. It does not explain the request format, error handling, or domain context (Google Play Android Developer API). More detail is needed for an agent to use it correctly.

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 coverage is 100% with descriptions for both parameters, so baseline is 3. The description adds no extra meaning beyond the schema; it does not explain the structure of the requests array or required fields in UpdateOneTimeProductRequest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('update'), resource ('one-time products'), and batch limit ('up to 100'). It distinguishes from singular update and other batch operations (delete, get) by name, but does not explicitly differentiate from other batch update tools (e.g., for offers).

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?

No guidance on when to use this tool vs. alternatives like onetime_products_update or other batch operations. No prerequisites mentioned (e.g., need for packageName). The description implies batch scenario but lacks explicit when-to or when-not-to context.

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

Deploy Server