Skip to main content
Glama
storelift-mcp

storelift-mcp

Recent reviews

get_reviews
Read-onlyIdempotent

Fetch App Store and Google Play reviews for one country, including text, ratings, dates and new-review counts, to track user feedback and rating trends.

Instructions

Recent reviews for one country: list holds the App Store reviews, android the Google Play reviews (a shorter window), each with its text, rating and date. newCount is how many arrived since the previous measurement; on an older record it arrives as null, so read it as unknown rather than zero. android: null means that Play page is awaiting its first measurement, and an empty list means the page has no reviews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "get_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesapp id from list_apps
countryNocountry code, e.g. tr, us (defaults to the app's first country)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • changedInput schema / properties / country / description
      Previous value: -"country code, e.g. tr, us"New value: +"country code, e.g. tr, us (defaults to the app's first country)"
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuine behavioral context: the android window is shorter, newCount means arrivals since the previous measurement, a null newCount on legacy records means unknown rather than zero, and null android versus an empty list are distinct states. It does not disclose any cap or pagination on how many reviews are returned, which is the remaining gap.

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?

Three sentences, front-loaded with what is returned, then edge-case semantics. Dense but each clause carries information; the field-by-field enumeration of text, rating and date is the only mildly expendable part.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only two parameters, the description does the heavy lifting of describing the return shape and its null/empty-list edge cases, which is the right place for that information. It stops short of noting any review-count limit or whether results are paginated, which for a "recent" list tool an agent could reasonably want.

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%, so appId and country (including the default-country behavior) are already documented in the schema. The description reinforces that results are scoped to a single country but adds no format or syntax detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recent reviews for one country" states a specific verb and resource, and the description goes on to name the two result collections (list / android) so the agent knows what it gets back. It never distinguishes itself from nearby siblings such as search_reviews, summarize_reviews or get_review_stats, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no pointer to search_reviews or summarize_reviews for agents that need filtered or aggregated reviews. Usage is only implied by the word "Recent", leaving the agent to infer the boundary against sibling tools.

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