Skip to main content
Glama

Get app metrics

get_app_metrics
Read-onlyIdempotent

Daily cached metrics for one app, at most 90 days (default 30). Installs are summed across versions. Revenue is net developer revenue grouped by original currency; amountMicros is an exact integer string (divide by 1,000,000). Active subscriptions are daily snapshots, not additive across dates. Missing rows mean unknown. At most 1000 rows per call. metric revenuecat reads the app's RevenueCat project (when connected in the app settings), across every store RevenueCat tracks and in the connection's single currency, kept apart from the store reports: mrrMicros, activeSubscriptions and activeTrials are end-of-day snapshots (never sum them across dates); revenueMicros, transactions and newCustomers are that day's flow; ARR is mrrMicros x 12 (RevenueCat's definition); activesAtStart and churnedActives (net paid subscriptions lost that day, can be negative) give churn = sum(churnedActives) / activesAtStart of the first day; paidTransactions and refundedTransactions (refunded since, counted on the purchase day) give the refund rate; trialStarts, trialConversions, trialExpirations, trialsPending describe the trials started that day; conversionCohort and payingCustomers are the customers first seen that day and those who paid within 7 days; recompute rates from summed counts, never average daily rates; null means RevenueCat returned no value; incomplete marks a day still accumulating; cohortIncomplete marks a day whose trials or customers can still convert; breakdown is the last 28 days of revenue split by store and country; platform does not apply and both platform grants are required.

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": {
      "appId": "<appId>",
      "metric": "<metric>"
    },
    "name": "get_app_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
appIdYes
metricYes
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / metric / enum
      Previous value: -[
      -  "installs",
      -  "revenue",
      -  "subscriptions"
      -]New value: +[
      +  "installs",
      +  "revenue",
      +  "subscriptions",
      +  "revenuecat"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantial context: caching, 90-day cap/default 30 days, 1000-row limit, missing/null/incomplete semantics, non-additive snapshots, and detailed RevenueCat caveats. This goes well beyond the annotations.

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

Conciseness3/5

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

It is front-loaded with the core behavior, but the RevenueCat section is a dense run-on with repeated snapshot warnings. Most details are relevant, yet the structure reduces readability.

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?

There is no output schema, so the description must explain return semantics; it does so extensively for the RevenueCat metric and caveats. It remains somewhat incomplete for output shape of non-RevenueCat metrics and has minor ambiguities.

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 description coverage is 0%, so the description must compensate. It explains the metric enum modes, the RevenueCat platform exception, date-range limits, and app scope, but from/to are only implied rather than explicitly named and the platform handling is somewhat ambiguous.

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

Purpose4/5

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

States it returns daily cached metrics for one app and gives the range bound (at most 90 days, default 30), with metric modes explained. It does not explicitly distinguish itself from sibling tools, though no sibling appears to cover app metrics.

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

Usage Guidelines3/5

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

The use case is implied: fetch app metrics. It gives operational constraints such as caching, row limits, and date bounds, but no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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.

Resources