Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apps_charts_item

Fetch one stored daily App Store or Google Play chart ranking row by chart_uid, using an exact ID from chart search results.

Instructions

Get one stored app-chart ranking. Retrieves one daily App Store or Google Play chart row by chart_uid from datasets_apps_charts_search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chart_uid": "<chart_uid>"
    },
    "name": "datasets_apps_charts_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_uidYesExact chart_uid from a search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose that entries are 'stored' daily chart snapshots from either App Store or Google Play, which tells the agent the data is a point-in-time ranking rather than live data. It says nothing about error behavior for a missing uid, permissions, or what fields a chart row returns.

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?

Two short sentences with the purpose front-loaded, followed by the source constraint. There is mild redundancy between 'Get one stored app-chart ranking' and 'Retrieves one daily ... chart row', which restate the same action.

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 single-item lookup with one required parameter and no output schema, the definition covers what the tool returns conceptually (one daily chart row from a named store) and where the key comes from. Only the concrete row fields and invalid-uid behavior are unstated, which is a modest gap for a tool this simple.

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% and the single parameter already documents 'Exact chart_uid from a search result', so the description repeats rather than extends that meaning. Baseline 3 applies since the schema does the semantic work for this one-parameter tool.

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 and resource ('Get one stored app-chart ranking') and further narrows it to 'one daily App Store or Google Play chart row' keyed by chart_uid. This is clearly distinguishable from the sibling search tool, which returns many rows.

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?

The definition implies the retrieval workflow by naming datasets_apps_charts_search as the source of chart_uid, and the schema reinforces this by requiring 'Exact chart_uid from a search result'. It does not explicitly state when not to use it or what to do with a stale/invalid uid, so it stops short of full 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

Other Tools