app-publish-mcp

google_list_subscriptions

Fetches all subscriptions for a Google Play Android app by package name, with pagination support to retrieve large lists.

Instructions

List all subscriptions for an app

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

Input Schema

Name	Required	Description
`pageSize`	No
`pageToken`	No	Pagination token from the previous response
`packageName`	Yes	Android package name

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Oct 25, 2026

addedInput schema / properties / pageSize

Added value: +{
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / pageToken

Added value: +{
+  "description": "Pagination token from the previous response",
+  "type": "string"
+}

First observedv0.3.1Mar 19, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description carries the full disclosure burden. It does not mention that the operation is read-only, paginated, or scoped by package name; 'list all' does not explain the pageSize/pageToken paging model. For a tool with zero annotation coverage, this is a significant gap.

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?

A single front-loaded sentence with zero filler; the scope ('for an app') is stated immediately. It is efficient, though its brevity reflects under-specification rather than deliberate economy.

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?

No annotations, no output schema, and an incomplete parameter picture (pageSize undocumented) mean the agent lacks the paging behavior and return-shape context it needs. The one-line description does not fill those gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, with packageName and pageToken documented in the schema but pageSize undocumented. The description only adds 'for an app', which loosely maps to packageName; it gives no explanation of the pagination parameters or how pageSize interacts with paging, so it does not compensate for the coverage gap.

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?

Clear verb+resource+scope: 'List all subscriptions for an app.' An agent understands this returns the subscription collection for a package name, distinguishable from singular google_get_subscription on the verb alone. However, it does not explicitly contrast with adjacent list tools like google_list_iap, so it falls short of a 5.

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 explicit when-to-use or when-to-avoid guidance and no named alternative. The agent must infer from the name that this lists subscriptions scoped to an app, with no hint about when to prefer it over google_list_iap or google_get_subscription.

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

Deploy Server