storelift-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appsA | List the apps tracked in this Storelift account (id, name, countries, keywords). Call this first — every other tool needs an appId from here. |
| get_keywordsA | Keyword ranks for one app in one App Store / Google Play country. THREE STATES ARE DISTINCT: measured=false means the query could not be measured, rank=null means it was measured but the app is absent from the top results, rank= is the rank. Never collapse them into one — counting an unmeasured day as zero produces a false answer. |
| get_rivalsA | Apps that rank ABOVE this app in search. For each rival you get the keywords it beats you on, its rank there (theirRank) and yours (ourRank) — ourRank null means the app does not appear for that keyword at all. |
| get_ai_visibilityA | Whether AI assistants name this app when asked natural questions about its category — reported per engine (Claude / ChatGPT / Gemini), never averaged. This is an OBSERVATION, not a ranking: a model's knowledge is frozen at a date and the answer is not identical every time, so read the trend rather than a single measurement. |
| get_historyA | Keyword rank history for one country. Series points are [day, rank]; a null rank means the app was absent from the top results that day, which is not the same as a bad rank. |
| get_store_pageA | The app's own store listing signals for one country: name, subtitle, version, in-app events, editorial placements, similar-apps shelves and the screenshot set (iOS), plus the Google Play page (exact install count, rating histogram, ad/IAP flags, chart badge). |
| get_reviewsA | Recent reviews for one country: |
| get_chartsA | App Store chart position for one country: current ranks per list (free / paid / grossing, overall and in category) plus their history. Google Play is absent on purpose — Google publishes no chart list, so there is nothing to read, and a number here would be invented. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| keywords_lost_ground | Which of my US keywords lost ground this week, and who is above me on them now? (uses get_keywords, get_history, get_rivals) |
| leader_listing | Show me the title, subtitle and keyword field of the app ranking first on my main keyword. (uses get_rivals, get_store_page) |
| crash_reviews | Summarise my recent reviews that mention a crash or a bug. (uses get_reviews) |
| category_chart | Where does my app sit in its category chart in Turkey? (uses get_charts) |
| ai_visibility | Do assistants name my app when asked about my category? (uses get_ai_visibility) |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct data resource: apps, AI visibility, keyword ranks, rivals, rank history, store listing, reviews, and charts. Even the two ranking-related tools are clearly separated as current vs historical, and get_rivals vs get_charts have unique purposes.
Seven tools use get_<resource> and one uses list_apps, a natural exception for enumerating all apps. All names are snake_case verb_noun pairs that are consistent and predictable.
8 tools is well-scoped for an app store analytics server; each tool covers a distinct measurable signal and none feels redundant. The set is neither too thin nor overloaded.
The surface covers the core Storelift workflow: enumerate apps, then inspect keyword ranks, history, rivals, store page, reviews, charts, and AI visibility. As a read-only analytics server, the lack of create/update/delete operations is not a gap.