Crawlora MCP

datasets_steam_reviews_item

Read-only

Fetch one stored Steam review by the exact app_id and recommendation_id returned by datasets_steam_reviews_search. The composite key identifies one review for a game; absent records return 404. Use datasets_steam_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": {
      "app_id": "<app_id>",
      "recommendation_id": "<recommendation_id>"
    },
    "name": "datasets_steam_reviews_item"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes	Required Steam app id returned by datasets_steam_reviews_search.
`recommendation_id`	Yes	Required recommendation_id returned by datasets_steam_reviews_search.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered, but the description adds genuinely new behavior: missing records return 404 and the key is a composite app_id + recommendation_id. Output shape need not be spelled out since an output schema exists.

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, zero filler, with the core action and key requirement front-loaded and the fallback/404 note and the search-routing hint following. Every sentence carries information.

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 two-parameter lookup with an output schema, this covers purpose, key composition, missing-record behavior, and how to obtain the ids. Only minor gap is no note on whether reviews can be edited/deleted between search and fetch.

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 both parameters are already documented as required ids returned by the search tool. The description's only added nuance is that the two fields form a composite key identifying one review for a game, which is marginal over the schema.

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 Steam review") plus the exact key it operates on, and distinguishes itself from the search sibling by emphasizing "one stored review" by composite key. An agent can tell instantly this is a single-record lookup, not a search.

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 routes the agent: it twice names datasets_steam_reviews_search as the source of the ids, making the prerequisite flow clear. It doesn't state when *not* to use it (e.g., when you want many reviews for a game), but the dependency guidance is strong.

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

All Crawlora MCP tools Inspect

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.