list_subscriptionsRetrieve all subscription products for an Android app using its package name to review current subscription offerings and billing configurations.
List all subscription products for an app.
| Name | Required | Description | Default |
|---|---|---|---|
| package_name | Yes | App package name |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden, and the verb 'List' clearly conveys a read-only, non-mutating operation. However, it does not disclose whether the result includes active and inactive products, pagination behavior, or permission requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no filler. The action, resource, and scope are all front-loaded, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter list operation with an output schema present, the description covers the core purpose and the parameter is fully documented. It is slightly thin on distinguishing this tool from sibling listing tools, but an agent has enough to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the only parameter as 'App package name' with 100% coverage. The description adds essentially no meaning beyond saying the listing is 'for an app,' so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific action ('List') and resource ('subscription products') scoped to 'an app.' It is clear at a high level and distinguishable from related siblings like get_subscription or list_subscription_offers, though it does not explicitly call out those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for an app' implies the context in which this tool is used, but the description provides no explicit guidance on when to use it versus list_subscription_offers, list_in_app_products, or get_subscription. It relies on the reader to infer usage from the wording.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.