mcp-livedatapro

getAppStoreMetrics

Live iOS App Store and Google Play Store rankings, download/revenue estimates, version history, and user reviews. Use when analyzing mobile application performance on Apple iOS App Store or Google Play Store, including chart rankings, monthly download/revenue estimates, and 1-star complaint themes. Do not use for open-source code packages (use getSoftwareReleases) or physical e-commerce product reviews (use getProductReviewsSentiment).

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": {
      "app_identifier": "<app_identifier>",
      "platform": "<platform>"
    },
    "name": "getAppStoreMetrics"
  }
}

Input Schema

Name	Required	Description	Default
`platform`	Yes	Target mobile application marketplace (ios or android).	ios
`app_identifier`	Yes	Exact mobile app bundle ID, package name, or numeric store ID (e.g., com.openai.chatgpt).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / app_identifier / examples
```
Added value: +[
+  "com.openai.chatgpt"
+]
```
- addedInput schema / properties / app_identifier / minLength
```
Added value: +3
```
- addedInput schema / properties / platform / default
```
Added value: +"ios"
```
- addedInput schema / properties / platform / enum
```
Added value: +[
+  "ios",
+  "android"
+]
```
- addedInput schema / properties / platform / examples
```
Added value: +[
+  "ios"
+]
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / app_identifier / description

Previous value: -"App name, bundle ID, or store ID (e.g., com.openai.chatgpt)"New value: +"Exact mobile app bundle ID, package name, or numeric store ID (e.g., com.openai.chatgpt)."

changedInput schema / properties / platform / description

Previous value: -"Target mobile app store"New value: +"Target mobile application marketplace (ios or android)."

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the data is 'live' and that download/revenue figures are estimates, but it does not mention authentication needs, rate limits, data freshness limits, pagination behavior, or what the response structure looks like.

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

Conciseness5/5

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

The description is three sentences and front-loads the data categories before stating usage and exclusions. Every sentence adds routing or scope information with no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter lookup with a fully described schema and no output schema, the description covers the data categories, usage conditions, and sibling exclusions well. It does not describe return format or pagination, but the tool's low complexity and complete schema make the description largely sufficient.

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 description coverage is 100%, so both parameters are already documented in the input schema, including the platform enum and app_identifier examples. The description reinforces the two store platforms but does not add format details beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (iOS App Store and Google Play Store metrics) and enumerates the data types returned: rankings, download/revenue estimates, version history, and user reviews. It also explicitly distinguishes the tool from sibling tools for software releases and product reviews, so an agent can identify its purpose without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit 'Use when' condition covering app performance analysis, chart rankings, monthly estimates, and complaint themes. It also provides clear exclusions with named alternatives: getSoftwareReleases for open-source packages and getProductReviewsSentiment for physical product reviews.

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

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?