Skip to main content
Glama

Get App Analytics

get_app_details
Read-only

Fetch SensorTower analytics for specific App Store apps using their numeric IDs. Returns downloads, revenue, ratings, and publisher info without scraping unnecessary apps.

Instructions

Fetch SensorTower analytics for one or more App Store app IDs. Returns downloads, revenue, ratings, publisher info, markets, and more for each app.

Use this when you already have app IDs (e.g. from search_app_store) and want detailed analytics for only a subset of them — avoiding unnecessary scrapes for apps you don't need. Use research_rivals instead for a single convenience call that searches and fetches analytics together. Do not use this for Google Play or Android apps — it takes numeric iOS App Store IDs only.

Requires a SensorTower account. The server opens a real Chromium window on the user's machine; the first run needs the user to log in there, and the session is reused from then on. If there is no session the call returns an error result carrying {"error": "not_logged_in"} and leaves the window open — tell the user to log in, then call again. Results are never cached, so every call scrapes fresh and costs roughly 10–20 seconds per app ID.

Returns JSON:

{
  "country": "us",
  "fetchedAt": "2026-04-21T10:00:00.000Z",
  "apps": [
    {
      "rank": 1,
      "name": "App Name",
      "appStoreUrl": "...",
      "sensorTowerUrl": "...",
      "downloads": "<5K",
      "revenue": "<$5K",
      "rating": { "score": "4.7", "count": "1,234" },
      "publisher": "Publisher Name",
      "categories": "Health & Fitness",
      "topMarkets": "United States, United Kingdom",
      "releaseDate": "Jan 1, 2020",
      "lastUpdated": "Mar 15, 2026",
      "languages": "English, Spanish",
      "inAppPurchases": "Monthly · $9.99",
      "publisherCountry": "United States",
      "advertisingNetworks": "N/A"
    }
  ]
}

Fields missing or gated behind a paywall will be "N/A". A single app failing to scrape is not fatal — that app comes back with "N/A" fields rather than failing the whole call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idsYesList of numeric App Store app IDs, as strings (e.g. ["123456", "789012"]). Each is the digits from an apps.apple.com URL's `id` segment, without the `id` prefix.
countryYesTwo-letter App Store country code (e.g. us, gb, tr)
Behavior5/5

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

Discloses behavioral traits beyond annotations: opens a real Chromium window, requires user login, session reuse, no caching, ~10-20 second cost per app ID. Explains error handling (non-fatal per-app failures, 'not_logged_in' error) and that missing/gated fields return 'N/A'. No contradiction with annotations.

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?

Well-structured with clear sections: purpose, usage guidelines, behavioral notes, and return format. Some redundancy (e.g., 'not for Google Play' repeated). Could be slightly trimmed but overall efficient.

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?

Very complete for a complex tool: provides full JSON return format, explains missing/gated fields, partial failures, use of Chromium, login flow, and performance characteristics. No output schema is needed given this level of detail.

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 coverage is 100% with clear descriptions. The description adds minor context (app IDs come from 'search_app_store', must be numeric without 'id' prefix) but does not significantly extend beyond schema. Baseline 3 is appropriate.

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 clearly states it fetches SensorTower analytics for one or more App Store app IDs, listing specific data points (downloads, revenue, ratings, etc.). It distinguishes itself from siblings like 'search_app_store' (for searching) and 'research_rivals' (combined search+analytics).

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?

Explicitly when to use (when app IDs are known) and when not (not for Google Play/Android). Provides alternatives ('research_rivals') and prerequisite: SensorTower account login. Also explains first-run login requirement and how to handle 'not_logged_in' error.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/meyusufdemirci/app-store-operator'

If you have feedback or need assistance with the MCP directory API, please join our Discord server