appstore-data
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Marketplace auth: sent as X-RapidAPI-Key + X-RapidAPI-Host. Required unless self-hosting. | |
| APPSTORE_API_HOST | No | Override the X-RapidAPI-Host value. | |
| APPSTORE_API_BASE_URL | No | Point at your own deployment instead of the marketplace. | |
| APPSTORE_PROXY_SECRET | No | Self-hosted origin auth (X-RapidAPI-Proxy-Secret). |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_appsA | Search a store by keyword, using the store's own relevance ranking. Returns compact rows with the id you need for get_app. |
| get_appA | Full metadata for one app: name, developer, ratings, price, version, size, screenshots, store URL. Use the numeric app id (iOS) or package name (Android). |
| get_app_reviewsA | Paginated user reviews. sort=recent is best for monitoring new feedback; sort=helpful surfaces the loudest complaints. Page with offset and stop when has_more is false. |
| top_chartsA | Ranked top-chart lists per storefront. iOS collections: topfreeapplications, toppaidapplications, topgrossingapplications, newapplications (+ ipad variants). Android: topselling_free, topselling_paid, topgrossing, new_free, new_paid. |
| list_categoriesA | The store's category taxonomy — id and name — for building filters or resolving a category id used by top_charts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: category taxonomy, keyword search, single-app metadata, paginated reviews, and ranked charts. Search vs. top charts are differentiated by intent (keyword relevance vs. storefront rankings), and search rows explicitly point to get_app for full details. No overlapping purposes remain.
Four of five tools follow a clear verb_noun convention (list_categories, search_apps, get_app, get_app_reviews). top_charts is a noun phrase rather than verb_noun, a minor deviation that is still readable and domain-idiomatic.
Five tools are well-scoped for an app-store data surface, with each operation earning its place. Discovery, detail, reviews, categories, and charts are all represented without redundant endpoints.
The read-only surface covers the full exploration lifecycle: taxonomy lookup, keyword search, full app metadata, review pagination, and ranked charts. No obvious gaps or dead ends for the stated app-store data purpose.