list_appsRetrieve the Google Play apps a service account can access based on its Play Console permissions, so you can see available apps before managing releases.
Lists the apps this service account can see, according to its Play permissions (Play Developer Reporting API apps:search).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful permission scoping and names the underlying API, but does not describe return shape, pagination, or ordering behavior for a list operation.
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?
A single front-loaded sentence with no filler; the permission scope and API reference are compact and relevant.
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 zero-parameter list tool with strong annotations, the description is nearly complete. The main minor gap is that it does not mention whether the result is paginated or what fields each app entry contains, though no output schema exists to cover that.
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 tool has zero parameters, so the baseline is 4. The description introduces no parameter confusion and correctly frames the tool as taking no inputs.
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 states a specific verb and resource ('Lists the apps') and adds scope ('this service account can see') plus the underlying API source. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling list/get tools.
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?
Usage is implied by the permission-scoped description, but there is no explicit guidance on when to choose this tool versus siblings like get_app_details or app_overview, nor any exclusions or prerequisites beyond Play permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.