Skip to main content
Glama
Sign In
google-play-developer-mcp

google-play-developer-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

onetime_products_batch_get

Retrieve details for up to 100 one-time in-app products from Google Play in one API call. Provide the package name and product IDs to batch-fetch product information.

Instructions

Fetch 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>",
      "productIds": "<productIds>"
    },
    "name": "onetime_products_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdsYes
packageNameYesAndroid application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Fetch' suggesting a read operation, but provides no detail on behavior (e.g., error handling, ordering, partial results). Minimal disclosure beyond the basic action.

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 a single concise sentence that front-loads the core purpose. Every word is necessary, with no superfluous content.

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?

Given the simple batch fetch operation and no output schema, the description is minimal. It does not explain return format, error scenarios, or differentiation from siblings beyond batch scope. Incomplete for comprehensive understanding.

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 documentation covers 50% (packageName described, productIds not). The description adds 'up to 100' which implies productIds are the list of IDs, but does not elaborate on format or constraints. Adds some value but not fully compensating for the gap.

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 'Fetch up to 100 one-time products in one call,' specifying the verb (fetch), resource (one-time products), and batch scope. This distinguishes it from sibling tools like onetime_products_get (single) and onetime_products_list (listing with possible filters).

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 implies batch fetching by IDs but lacks explicit guidance on when to use this tool versus alternatives. It does not mention when-not-to-use or name alternative tools like onetime_products_list for different use cases.

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