Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

datasets_apps_reviews_search

Search iOS App Store and Google Play user reviews by keyword, app, country, rating, or sort order to analyze app feedback and sentiment.

Instructions

Search the app-reviews dataset. Searches user reviews from the iOS App Store and Google Play (one document per review). Store enum: ios, android. Sort enum: recent, score_desc, score_asc, helpful_desc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

Name	Required	Description
`q`	No	Full-text query over review text, title and author, max 256 characters
`page`	No	Page number, defaults to 1
`sort`	No	Sort enum: recent, score_desc, score_asc, helpful_desc
`store`	No	Store enum: ios, android
`app_id`	No	Exact app filter — iOS numeric track id or Android package, max 128 characters
`country`	No	Exact storefront country filter, max 128 characters
`min_score`	No	Minimum star rating, 1 through 5
`page_size`	No	Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.17.5Sep 26, 2026
- addedInput schema / properties / sort / enum
```
Added value: +[
+  "recent",
+  "score_desc",
+  "score_asc",
+  "helpful_desc"
+]
```
- addedInput schema / properties / store / enum
```
Added value: +[
+  "ios",
+  "android"
+]
```
Addedv1.2.0Jul 6, 2026

TDQS

A3.6/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 it does disclose a genuinely non-obvious behavioral trait: the credit cost model (1 credit per record, minimum 2, empty result costs 2, full page of 100 costs 100). This materially affects how an agent should size queries. It still omits auth/permission requirements and pagination behavior.

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?

Four sentences, front-loaded with purpose and data source, then enums, then cost. The verbatim enum restatement is mildly redundant against the schema, but nothing is buried and the cost caveat lands clearly.

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 0-required-param search tool with a fully described schema and no output schema, the description covers purpose, source, and cost. However, it leaves the key cross-tool decision (reviews vs. app metadata searches) unaddressed, which is the main gap an agent would hit.

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 the schema already documents all 8 parameters. The description merely restates the store and sort enums verbatim, and its billing note implies a page_size/cost relationship but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb ('Search') and resource ('app-reviews dataset'), then sharpens it with the data source and granularity: user reviews from the iOS App Store and Google Play, one document per review. This clearly separates it from content-type siblings like datasets_apps_search or datasets_apps_charts_search without needing to name them.

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?

The description never says when to choose this tool over alternatives such as datasets_apps_search or appstore_reviews/googleplay_reviews, nor any prerequisites or exclusions. It gives enum values and cost, but no routing guidance.

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

Deploy Server

datasets_apps_reviews_search

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools