Skip to main content
Glama
storelift-mcp

storelift-mcp

Revenue and downloads

get_revenue
Read-onlyIdempotent

Retrieve revenue and downloads for one app from your connected App Store Connect, Google Play and RevenueCat sources, including MRR, subscriptions and trials. Shows only measured data, never estimates.

Instructions

Revenue and downloads for one app from the sources the user connected: App Store Connect daily units per country, Google Play daily installs, and RevenueCat MRR, 28-day revenue, active subscriptions and trials with the MRR movement breakdown. connected=false means no source is connected; measured=false means the sources hold no rows for this app. Nothing here is estimated.

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>"
    },
    "name": "get_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNohow many days of daily series to return, from 1 up to the plan's history window (default 90)
appIdYesapp id from list_apps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.2
    • changedInput schema / properties / days / description
      Previous value: -"how many days of daily series to return, 1–365 (default 90)"New value: +"how many days of daily series to return, from 1 up to the plan's history window (default 90)"
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the description's job is to add context — and it does: it defines connected=false, measured=false, and states nothing is estimated, which tells the agent how to interpret empty or missing results. It stops short of covering the response shape beyond a metric list or any rate/limit behavior, so it is strong but not exhaustive.

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

Conciseness4/5

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

Three sentences with the source-to-metric mapping front-loaded and no filler; every clause carries information. The single long enumerating sentence is dense but still parseable, which is the only minor cost.

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?

With no output schema, the description carries the return-value burden and does so by listing each returned metric family, plus edge-case semantics for unconnected sources and empty data. What is missing is small: no indication of ordering, pagination, or how the days window interacts with the plan history limit.

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% and the schema already documents both days (range, default 90, plan history window) and appId (from list_apps), so the baseline of 3 applies. The description adds only an incidental hint that the result is a 'daily series' without new syntax or bounds beyond the schema.

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?

The description names a specific resource (revenue and downloads for one app) and enumerates exactly which figures come from which source (App Store Connect daily units per country, Google Play daily installs, RevenueCat MRR/28-day revenue/subscriptions/trials plus MRR movement). It is clearly scoped to a single app, but it never names a sibling to distinguish itself from aggregation tools like get_portfolio_overview or get_subscription_events.

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?

Usage context is implied by the 'from the sources the user connected' framing and the single-app scope, so an agent can infer this is the per-app revenue/downloads read. There is no explicit when-to-use versus an alternative, and no note on prerequisites such as requiring a connected source before calling.

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