Crawlora MCP

Official

by Crawlora-org

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

datasets_apps_reviews_item

Retrieves one stored public App Store or Google Play review by review_uid from a prior search result.

Instructions

Get one stored app review. Retrieves one public App Store or Google Play review by review_uid from datasets_apps_reviews_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": {
      "review_uid": "<review_uid>"
    },
    "name": "datasets_apps_reviews_item"
  }
}

Input Schema

Name	Required	Description	Default
`review_uid`	Yes	Exact review_uid from a search result

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden, and it does disclose that the review is stored and public and may come from either the App Store or Google Play. However, it does not mention error behavior, authentication needs, rate limits, or what happens when a `review_uid` is not found.

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 definition is two short sentences with no wasted wording, and the core action is front-loaded before the source-tool clarification. It is appropriately sized for a simple one-parameter lookup.

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 simple item-retrieval tool with one required parameter, no output schema, and a fully described schema, the description is largely complete enough to support correct invocation. It could be stronger by noting error or not-found behavior, but no major operational gap remains.

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 is already documented as the exact `review_uid` from a search result. The description reinforces that meaning but does not add syntax, format, or constraints beyond what the schema provides.

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 uses a specific verb and resource: "Get one stored app review," then clarifies it retrieves one public App Store or Google Play review. It also distinguishes this item lookup from the sibling search tool by naming `datasets_apps_reviews_search` as the source of the `review_uid`.

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 description clearly indicates this tool is for retrieving a single review after obtaining a `review_uid` from `datasets_apps_reviews_search`. It does not explicitly state when not to use it or describe failure cases, but the usage context is sufficiently clear for an item-fetch tool.

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

Deploy Server