Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apps_search

Search the apps-intelligence dataset. Searches resolved iOS App Store and Google Play apps stored in a search index. Store enum: ios, android, both.

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. 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

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

B3.3/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 disclose the most consequential behavioral trait: the credit cost model (1 credit/record, minimum 2, empty result costs 2, full 100-record page costs 100). It also discloses that platforms applies only to ios records. It omits auth/permission requirements and rate-limit behavior, keeping it short of a 5.

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

Conciseness3/5

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

Front-loaded and readable, but three full sentences are spent restating enum values that already exist in the structured schema, which is redundant. The billing sentence, by contrast, earns its place.

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?

All 12 parameters are covered (schema plus enum recap) and the billing model is explained, but with no output schema the description should say something about what a result record contains and give sibling routing among the apps datasets family; both are absent.

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 12 params, and the description largely re-lists the store/platform/sort enum values verbatim rather than adding syntax. The one genuine addition beyond the schema is that the platform filter applies only to ios records.

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?

States a specific verb (Search) and resource (resolved iOS App Store and Google Play apps in a search index), which is clearer than a generic 'search apps'. However it never distinguishes itself from close siblings like datasets_apps_charts_search or datasets_apps_reviews_search, so an agent must infer the boundary.

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?

No when-to-use guidance, no exclusions, and no routing to the two sibling apps datasets tools that operate on the same underlying data. The enum and billing notes are field-level detail, not usage guidance.

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