app-publish-mcp

google_get_subscription

Retrieve details of a specific subscription from Google Play Console by providing the Android package name and subscription product ID.

Instructions

Get details of a specific subscription

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

Input Schema

Name	Required	Description	Default
`productId`	Yes	Subscription product ID
`packageName`	Yes	Android package name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

C2.9/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 implies a read operation ('Get') but does not disclose behavioral traits such as permission requirements, rate limits, or whether it is read-only. Additional context would be beneficial.

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

Conciseness4/5

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

Single sentence, no wasted words. Purpose is front-loaded. Could be slightly more efficient by omitting 'of a', but overall concise.

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?

No output schema, yet description does not hint at return value (e.g., subscription details object). For a simple get tool, this is marginally adequate but could be more complete by mentioning what information is retrieved.

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 clear parameter descriptions ('Android package name', 'Subscription product ID'). The description adds no extra meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 'Get details of a specific subscription', using a specific verb and resource. It distinguishes from siblings like 'google_list_subscriptions' (lists all) and 'google_get_iap' (for IAPs), but does not explicitly mention the parameters that identify the subscription.

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 versus alternatives like 'google_list_subscriptions' or other get tools. The description simply states what it does without context for selection.

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

Deploy Server