Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apps_charts_search

Search daily iOS App Store and Google Play chart snapshots to retrieve app ranks by date, chart type, country, category, store, or app ID, including rank history.

Instructions

Search the app-charts dataset. Searches daily top-chart snapshots from the iOS App Store and Google Play (one document per chart × snapshot × rank). With no date the latest snapshot is returned (today's chart); pair app_id with sort=date_desc for an app's rank over time. Store enum: ios, android. Chart type enum: top_free, top_paid, top_grossing, new. Platform enum (Apple device platforms, ios charts only): phone, pad, mac. Sort enum: rank, rank_desc, date_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

NameRequiredDescriptionDefault
qNoFull-text query over chart-entry title and developer, max 256 characters
dateNoSnapshot date filter yyyy-MM-dd; defaults to the latest snapshot
pageNoPage number, defaults to 1
sortNoSort enum: rank, rank_desc, date_desc
storeNoStore enum: ios, android
app_idNoExact app filter — iOS numeric track id or Android package; pair with sort=date_desc for rank history
countryNoExact storefront country filter, max 128 characters
categoryNoStore category/genre filter, max 128 characters; empty for the overall charts
platformNoApple device-platform filter, iOS charts only; see platform enum above
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
chart_typeNoChart enum: top_free, top_paid, top_grossing, new
collectionNoRaw store collection id filter (e.g. topgrossingapplications, GROSSING), max 128 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / chart_type / enum
      Added value: +[
+  "top_free",
+  "top_paid",
+  "top_grossing",
+  "new"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "rank",
+  "rank_desc",
+  "date_desc"
+]
    • addedInput schema / properties / store / enum
      Added value: +[
+  "ios",
+  "android"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Apple device-platform filter, iOS charts only; see platform enum above",
+  "type": "string"
+}
  3. Addedv1.2.0

TDQS

A4.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 well: it discloses the credit-based billing model (1 credit per record, minimum 2, empty result costs 2, full page of 100 costs 100) and the latest-snapshot default. It does not cover permissions or what the returned records contain, so it is strong but not exhaustive.

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?

Front-loads purpose, then behavior, then enums, then billing — a sensible order. The store/chart_type/platform/sort enum lists are repeated verbatim from the schema, which is mild redundancy, keeping it from a 5.

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?

For a 12-parameter tool with no annotations and no output schema, the description covers purpose, defaults, interaction patterns, filters, and cost — enough for an agent to invoke it correctly. Return-record shape is left unaddressed, but the scope constraints the agent needs are present.

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; the description adds marginal framing by restating enum values and combining parameters into patterns (app_id + sort=date_desc, platform valid only for ios charts). Much of this duplicates schema text, but the cross-parameter usage framing adds some interpretable value.

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 precise verb and resource ('Search the app-charts dataset') and defines the underlying data model — daily top-chart snapshots from the iOS App Store and Google Play, one document per chart × snapshot × rank. This granular description of contents distinguishes it from the sibling datasets_apps_search without needing to name it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage patterns: 'With no date the latest snapshot is returned' and 'pair app_id with sort=date_desc for an app's rank over time', telling the agent how to hit common goals. It lacks explicit when-not guidance or a named alternative (e.g., routing app metadata lookups to datasets_apps_search), so it stops short of a 5.

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