Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

datasets_apps_reviews_item

Read-only

Fetch one stored App Store or Google Play review by its exact review_uid from datasets_apps_reviews_search. The response is the full stored review record; absent ids return 404. Use datasets_apps_reviews_search to find review ids.

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

NameRequiredDescriptionDefault
review_uidYesRequired exact review_uid returned by datasets_apps_reviews_search.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the readOnlyHint/openWorldHint annotations: the response is the full stored record and a missing id yields a 404. That failure mode is the main thing an agent needs to handle, and it is documented. Minor gap: no note on whether retrieval is instant or cached, but nothing material.

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?

Three short sentences, front-loaded with what it does, then the id source, then the failure mode. Nothing is redundant and every sentence carries information.

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?

The tool is a simple one-param lookup with an output schema and annotations, so the description covers what matters. However, it doesn't distinguish this dataset-level review item from per-store siblings like appstore_reviews or googleplay_reviews, which an agent in this crowded namespace might reasonably confuse it with.

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% and the single parameter is already documented, so baseline is 3. The description adds provenance ('from datasets_apps_reviews_search') and stresses exactness, which helps the agent avoid guessing or fabricating uids — a meaningful bump over the schema text.

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 ('Fetch one stored App Store or Google Play review') and pins the identifier ('exact review_uid'), which cleanly distinguishes it from the sibling datasets_apps_reviews_search that returns lists.

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?

Explicitly names the prerequisite path: get the id from datasets_apps_reviews_search, then call this. That is a clear routing instruction, though it does not state outright when not to use this tool (e.g., when you only have an app id and need to list reviews first).

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources