get_v2_app_analytics_app_storeApp Analytics / App Store Group: Mobile Apps. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| app_id | No | You can find app IDs by searching from the Autocomplete endpoint. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description gives no behavioral details. It does not state whether the tool is read-only, what data it returns, or any side effects. The billing note is cost information, not behavioral disclosure.
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 extremely short but under-specified rather than appropriately concise. It fails to front-load purpose or provide any actionable information. It is more of a label than a description.
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 tool with a simple input and no output schema, the description still needs to explain what analytics are provided and what the user can expect. It gives no context about the output or use case, making it inadequate.
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?
Schema description coverage is 100%, so baseline is 3. However, the description adds no parameter context beyond what the schema already provides. The schema's parameter description is helpful, but the tool description contributes nothing.
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 'App Analytics / App Store Group: Mobile Apps' essentially restates the tool name without specifying a clear action or resource. It lacks a verb and does not differentiate from siblings like Google Play analytics. This is a tautology.
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?
No guidance is provided on when to use this tool versus alternatives such as get_v2_app_analytics_google_play or get_v2_app_store_app_details. There is no mention of use cases, exclusions, or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.