Skip to main content
Glama

Research App Store Rivals

research_rivals
Read-only

Search the App Store for a keyword and get SensorTower analytics for top competing apps — all in one call.

Instructions

Search the App Store for a keyword and fetch SensorTower analytics for the top results — all in one call. Results are cached for 24 hours so repeat queries are instant.

Use this for a quick competitive overview when you want everything in one step. Use search_app_store + get_app_details separately when you need more than 3 results, a custom limit, or selective fetching of specific apps. Do not use this for Google Play or Android apps — it covers the iOS App Store only.

Requires a SensorTower account. On a cache miss 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. A cache miss scrapes three apps and typically takes 30–60 seconds; a cache hit returns immediately and opens no browser.

Trigger phrases: "rival research", "research rivals", "competitor analysis", "find competing apps", "check competitors", "what apps compete with", "App Store competitors", "rivals for keyword".

Returns JSON:

{
  "keyword": "meditation",
  "country": "us",
  "fetchedAt": "2026-04-21T10:00:00.000Z",
  "cached": false,
  "apps": [
    {
      "rank": 1,
      "name": "App Name",
      "appStoreUrl": "https://apps.apple.com/us/app/id123456",
      "sensorTowerUrl": "https://app.sensortower.com/overview/123456",
      "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. When cached is true, the data was served from the local cache and no scraping occurred.

Present results as a clean report for each app:


#1 — {name}

  • App Store: {appStoreUrl}

  • SensorTower: {sensorTowerUrl}

  • Downloads: {downloads}

  • Revenue: {revenue}

  • Rating: {rating.score} ({rating.count} ratings)

  • Publisher: {publisher}

  • Categories: {categories}

  • Top Markets: {topMarkets}

  • Worldwide Release Date: {releaseDate}

  • Last Updated: {lastUpdated}

  • Languages: {languages}

  • In-App Purchases: {inAppPurchases}

  • Publisher Country: {publisherCountry}

  • Advertised on Any Network: {advertisingNetworks}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesTwo-letter App Store country code (e.g. us, gb, tr)
keywordYesThe keyword to search in the App Store (e.g. psikoloji, meditation)
Behavior5/5

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

Discloses caching (24h), browser opening on cache miss, login requirement, error handling for not_logged_in, time estimates, and behavior when apps fail. No contradiction with annotations (readOnlyHint and openWorldHint are consistent with reading data and client-side side effects).

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?

Well-structured with clear sections: purpose, caching, usage, prerequisites, behavior, output example, and presentation format. Every sentence adds value and it is front-loaded with the main action.

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?

Covers all necessary context: complexity of combined APIs, caching, authentication, browser opening, error states, time expectations, and output interpretation. Despite no output schema, the detailed JSON example and field notes ensure completeness.

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 descriptions for both parameters; the description adds minimal extra beyond schema (examples like 'psikoloji, meditation' and reaffirms country code format), so 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 the tool combines App Store search and SensorTower analytics in one call, and distinguishes from sibling tools (search_app_store + get_app_details) by specifying it is for quick overviews with 3 results.

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 provides when to use (quick competitive overview, one step) and when not to use (need more than 3 results, custom limit, selective fetching), and notes it only covers iOS App Store.

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