Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apps_search

Find and filter apps across iOS and Android stores by platform, rating, reviews, category, and developer. Access structured app data for analysis.

Instructions

Search the apps-intelligence dataset. Searches resolved iOS App Store and Google Play apps stored in a search index. Store enum: ios, android, both. Platform enum (Apple device platforms, ios records only): phone, pad, mac, tv, watch, vision. Sort enum: relevance, rating_desc, reviews_desc, installs_desc, updated_at_desc, popularity_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over title, developer and category, max 256 characters
freeNoFilter by price; true keeps only free apps, false only paid
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rating_desc, reviews_desc, installs_desc, updated_at_desc, popularity_desc
storeNoStore enum: ios, android, both
countryNoExact storefront country filter, max 128 characters
categoryNoExact app-store category filter, max 128 characters
developerNoExact developer/publisher name filter, max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
platformsNoRepeatable Apple device-platform filter (OR); see platform enum above
min_ratingNoMinimum store rating, 0 through 5
min_reviewsNoMinimum ratings/review count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / platforms / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "rating_desc",
+  "reviews_desc",
+  "installs_desc",
+  "updated_at_desc",
+  "popularity_desc"
+]
    • addedInput schema / properties / store / enum
      Added value: +[
+  "ios",
+  "android",
+  "both"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / platforms
      Added value: +{
+  "description": "Repeatable Apple device-platform filter (OR); see platform enum above",
+  "type": "array"
+}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort enum: relevance, rating_desc, reviews_desc, installs_desc, updated_at_desc"New value: +"Sort enum: relevance, rating_desc, reviews_desc, installs_desc, updated_at_desc, popularity_desc"
  3. Addedv1.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full responsibility for behavioral disclosure. It only states that it 'searches ... stored in a search index', which gives some context but no details about read-only nature, pagination behavior, ordering defaults, or what the response structure looks like. For a search tool with 12 optional parameters, this is a significant gap.

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?

The description is concise, front-loaded with the primary purpose, and then enumerates the key enums. It avoids redundancy and is easy to scan. Every sentence contributes to clarifying what the tool does.

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 12 parameters and no output schema, the description covers the enum values but omits context about result format, pagination limits (e.g., page_size max), or default behaviors that agents might need. The schema handles parameter details, but the description does not hint at what a successful response looks like. The tool is complex enough that this missing context makes it only minimally complete.

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 description coverage is 100%, so the baseline is 3. The description adds value by explicitly listing the allowed values for the 'platform' enum (which the schema only declares as a string array) and repeating store and sort enums (also in the schema but useful for quick reference). This goes beyond simply echoing the schema, justifying a 4.

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 clearly states the tool's purpose: 'Search the apps-intelligence dataset. Searches resolved iOS App Store and Google Play apps stored in a search index.' This specifies a verb (search), a resource (apps-intelligence dataset), and the scope of data (resolved iOS/Google Play apps). It distinguishes itself from siblings like datasets_apps_charts_search and datasets_apps_reviews_search by being a general search over apps, not a specific chart or review search.

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 provides no explicit guidance on when to use this tool versus alternatives (e.g., datasets_apps_charts_search or datasets_apps_reviews_search). It does not mention exclusions, alternative tools, or conditions for choosing this search. The only implicit hint is its scope (general app search), but no clear direction is given.

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