Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_reviews

Retrieve App Store customer reviews for an app by numeric track ID or bundle ID. Returns one page of reviews, sortable by most recent or most helpful.

Instructions

Retrieve App Store reviews. Returns one page of customer reviews for an app. Provide either id (numeric track ID) or app_id (bundle ID).

Input Schema

TableJSON 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

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions 'Returns one page' which implies pagination, but doesn't disclose the page range (1-10 from schema) or behavior when both id and app_id are supplied. It also doesn't state that this is a read-only operation. This is a minimal disclosure but not misleading.

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: the first states purpose, the second gives parameter guidance. It is front-loaded with the core action and keeps extra detail to a minimum. No wasted words.

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

Completeness3/5

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

For a tool with 6 parameters and no output schema, the description is adequate but leaves gaps: it doesn't mention defaults for lang/country, the page range (though schema covers it), or what happens if both identifiers are provided or if none are. It also doesn't hint at the return format. These are minor for a simple retrieval but could be more complete.

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% for all 6 parameters, so the baseline is 3. The description adds value by clarifying that either id or app_id should be provided, and explains what they mean. It does not add further semantics for lang, page, sort, or country beyond what the schema already says.

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 ('Retrieve') and resource ('App Store reviews'), and clarifies it returns one page of customer reviews for an app. It does not explicitly differentiate from sibling tools like appstore_ratings or appstore_app, but the purpose is unambiguous.

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?

The description provides guidance on which identifier to use (either id or app_id), which is helpful. However, it does not specify when to choose this tool over alternatives (e.g., appstore_ratings for aggregate ratings) or what happens if neither parameter is provided. There's no explicit when-not or alternative routing.

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