Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

appstore_ratings

Retrieve an App Store app's total ratings and 1-5 star histogram by numeric track ID or bundle ID. Use optional country and language filters.

Instructions

Retrieve App Store ratings histogram. Returns the total ratings count and the 1 to 5 star histogram for an App Store app. Identify it with either the numeric track id or the bundle ID app_id; a bundle ID is resolved to the track ID first, and a non-numeric id returns 400. country and lang are optional.

Input Schema

NameRequiredDescriptionDefault
idNoApp Store numeric track ID (digits only)
langNoResult language tag
app_idNoApp Store bundle ID
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose non-obvious traits: bundle IDs are resolved to a track ID first, and a non-numeric `id` returns a 400. That resolution and error behavior go beyond what the schema signals, though auth and rate-limit context are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, then return shape, then identifier mechanics. Every sentence adds information and none is filler.

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 no annotations, the description compensates well by describing the returned `ratings` count and `histogram`, the identifier options, and the error case. It is nearly complete for a read tool; only auth/rate-limit details are unmentioned.

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 real meaning: it frames `id` and `app_id` as alternative identifiers, explains the bundle-ID-to-track-ID resolution order, and notes the 400 on non-numeric `id`. This exceeds the schema's terse field descriptions.

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

Purpose5/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 ('Retrieve App Store ratings histogram') and immediately clarifies the return shape (total `ratings` count plus 1-5 star `histogram`). This cleanly separates it from siblings like appstore_reviews or appstore_app, which cover text reviews or app metadata rather than the ratings distribution.

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 by the narrow purpose and by the guidance on identifying the app (numeric `id` vs. bundle `app_id`), but no explicit when-to-use or alternative is named (e.g., pointing to appstore_reviews for written reviews). An agent could infer the fit, but nothing routes it away from wrong siblings.

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