Skip to main content
Glama
App Store and Google Play Review Monitor MCP Server

App Store and Google Play Review Monitor MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
monitor_app_reviewsA

Return App Store and Google Play reviews for the apps you give, by country store, newest first. Give apps as App Store URLs or ids (id618783545) or Google Play URLs or package names (com.Slack). With a state_key, each run returns only reviews not returned by an earlier run with that key. Every review row carries stars, title, text, author, app version, date, helpful votes, the Google Play developer reply, and the developer name, website, and domain. One app_summary row per app and country store gives the app rating, rating count, change since the last run, and the star split of the new reviews. Google Play reviews are per language, so they come back once under the first country. Input with no app comes back as one free row with error_reason input_invalid. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per review row and per app trend row.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusing it with another. Its description clearly frames it as a read-only review retrieval operation for two named app stores.

Naming Consistency5/5

The single name monitor_app_reviews follows a clean verb_noun snake_case convention that reads predictably and matches the domain. No competing conventions exist to clash with it.

Tool Count4/5

A single, purpose-built tool is appropriate for a narrowly scoped review-monitoring service, and this one is feature-dense (both stores, incremental state, summaries). It falls just short of the ideal 3-15 range, though adding tools here would likely be artificial.

Completeness4/5

The tool covers the full read path: fetch reviews, track new-vs-seen via state_key, and return per-app/country trend summaries with rich row fields. Minor gaps exist — no way to inspect or reset a state_key, no app lookup/metadata, and read-only by design — but core monitoring workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessOutdated data