Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_reviews

Retrieve one page of App Store customer reviews by numeric track ID or bundle ID, with page and sort filters, to inspect ratings and user feedback.

Instructions

Retrieve App Store reviews. Returns one page of customer reviews for an App Store app, identified by id (numeric track ID) or app_id (bundle ID). page runs 1 to 10 and sort is mostRecent (default) or mostHelpful. Reviews carry score, title, text, version, user_name and updated. Returns 503 when reviews cannot be retrieved, and 404 when the app is not in that country storefront.

Input Schema

NameRequiredDescriptionDefault
idNoApp Store numeric track ID (digits only)
langNoResult language tag
pageNoReview page number (1-10)
sortNoSort order
app_idNoApp Store bundle ID
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "mostRecent",
+  "mostHelpful"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does it well: it discloses pagination ("one page", page 1-10), the returned review fields (score, title, text, version, user_name, updated), and two failure modes (503 cannot retrieve, 404 not in that country storefront). It stops short of rate limits or auth requirements, but the disclosure of return shape and error behavior is substantial.

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?

Front-loaded with the core action, then progressively adds identification, pagination, return fields, and error semantics. Every sentence carries information, though the review-field enumeration makes it slightly dense rather than maximally tight.

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?

For a 6-param tool with no annotations and no output schema, the description covers the essential return shape, pagination bounds, sort default, and error cases. The only real gap is the `lang` parameter, which is never mentioned in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value by naming the default sort ("mostRecent (default)") and linking `country` to the 404 behavior, which the schema does not. The id/app_id and page-range notes largely restate the schema.

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 opens with a specific verb+resource ("Retrieve App Store reviews") and immediately scopes it ("one page of customer reviews for an App Store app"), so an agent knows exactly what it does. It does not, however, explicitly differentiate itself from sibling review/app tools like appstore_ratings or appstore_app.

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?

It provides operating context (identification by id or app_id, page range, sort options, error codes) that implicitly guides use, but never states when this tool is preferred over alternatives or any exclusions. The agent must infer that this is the reviews-specific endpoint.

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

Deploy Server

Other Tools