Skip to main content
Glama

App revenue estimate

app_metrics_revenue_worldwide
Read-only

An app's estimated revenue from store purchases over the last 30 days: worldwide gross (what users paid) and net (what the developer keeps after the store's commission), each with a low–high range and a size bucket, plus the split by country, largest first. Neither store publishes revenue, so these are estimates on both stores: approximate for any single app, best for sizing an app or comparing apps, and to be presented to the user as estimates. An app the store lists no purchases for reads 0. Figures are in USD unless currency is given. Costs 10 credits.

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": {
      "store": "<store>",
      "package": "<package>"
    },
    "name": "app_metrics_revenue_worldwide"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many countries to return, up to 250. 50 by default.
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
packageYesApp package / bundle id, e.g. "com.discord" (Android) or a numeric App Store id. If you only have the app name, call app_search first to resolve it.
currencyNoCurrency of the figures, an ISO 4217 code such as "EUR" or "GBP". USD by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that neither store publishes revenue so these are modeled estimates, how to present them, that a no-purchase app reads 0, the default currency, and the cost of 10 credits. These are exactly the behavioral facts an agent needs before quoting figures to a user.

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 purpose and the returned structure are front-loaded in the first sentence, followed by estimation caveats, edge case, currency default, and cost. No sentence is filler, despite the density.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values and does so thoroughly: gross/net, range, bucket, country ordering. Combined with the estimation caveat and cost, nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by stating the country split is ordered largest first and that figures are USD unless `currency` is supplied, which clarifies the semantics of `limit` and `currency` beyond the bare schema text.

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 opening clause names a specific resource and metric: an app's estimated revenue from store purchases over the last 30 days, broken into `gross`/`net`, `low`–`high` range, `bucket`, and per-country split. That is clearly distinct from siblings like app_metrics_installs_history or app_metrics_ratings_worldwide, which cover different metrics.

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

Usage Guidelines4/5

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

It states the appropriate use case explicitly: 'best for sizing an app or comparing apps,' with an explicit caution that single-app figures are approximate and must be presented to the user as estimates. It also notes the zero-purchase case. It does not name sibling alternatives directly, but the intended context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.