Skip to main content
Glama
storelift-mcp

storelift-mcp

Search reviews

search_reviews
Read-onlyIdempotent

Find an app's reviews in a storefront by text, star rating, version or date range, newest first, and see whether more matched than the row limit returned.

Instructions

Search one app's reviews in one storefront by text, star rating, app version and date range, newest first — up to 1,000 rows from the full review archive within your plan's review window. total is the match count; truncated tells you when more rows matched than you asked for.

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": "search_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNotext to find in the review title or body
toNolast day, YYYY-MM-DD
fromNofirst day, YYYY-MM-DD
appIdYesapp id from list_apps
limitNorows, up to 1000 (default 100)
ratingNostar ratings, comma separated, e.g. 1,2
countryNocountry code, e.g. tr, us (defaults to the app's first country)
versionNoapp version the review was written on, e.g. 2.4.0
platformNodefaults to ios

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds real value: deterministic ordering (newest first), a hard 1,000-row ceiling, the constraint that results are limited to the plan's review window, and the meaning of the `total` and `truncated` return fields. It omits pagination mechanics and what the review records contain, but the essentials are disclosed.

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?

Two sentences and a short clause, front-loaded with the scope and filters before the row cap and return-field semantics. Every element carries information, though the return-value sentence could be tighter.

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 9 parameters, one required, and no output schema, the description does well: it names the filter surface, the ordering, the result ceiling, and the two response metadata fields. The remaining gap is that it never points the agent to sibling tools for unfiltered or summarized review access.

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 description coverage is 100%, so every parameter is already documented in the input schema, which sets the baseline at 3. The description adds the ordering semantics and the limit ceiling context but does not explain interactions between parameters, such as how date range and version combine or how comma-separated ratings behave.

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?

The description states a specific verb and resource ("Search one app's reviews in one storefront") and immediately enumerates the filterable dimensions (text, star rating, app version, date range), so an agent knows exactly what the tool does. It does not explicitly contrast with sibling tools like get_reviews or summarize_reviews, 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 Guidelines3/5

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

Usage is implied rather than stated: the phrase "Search one app's reviews in one storefront" signals a filtered retrieval pattern, and the row cap hints at bounded exports. However, there is no explicit when-to-use versus get_reviews, summarize_reviews, or export_data, and no stated prerequisites or exclusions.

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