Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

datasets_steam_reviews_item

Retrieve a single stored Steam recommendation review by app ID and recommendation ID, enabling detail lookup from prior review search results.

Instructions

Get one stored Steam review. Retrieves one stored recommendation review using appid and recommendation_id from datasets_steam_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": {
      "app_id": "<app_id>",
      "recommendation_id": "<recommendation_id>"
    },
    "name": "datasets_steam_reviews_item"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes	Steam app id
`recommendation_id`	Yes	Steam recommendation id

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that reviews are 'stored' (i.e., served from a dataset rather than a live Steam call). It says nothing about behavior for a missing recommendation id, error responses, or what fields a review contains.

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 core action front-loaded. The second sentence largely restates the first before adding the useful id-provenance note, so there is mild redundancy but no wasted bulk.

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?

For a two-parameter single-record getter with no output schema, the definition covers the essential action and id source. It leaves gaps around failure modes for unknown ids and what a returned review looks like, which matters because there are no annotations to fall back on.

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%, so both parameters are already documented, making 3 the baseline. The description adds provenance value by tying the ids to the search tool, but it writes `appid` while the schema uses `app_id`, a minor inconsistency that adds no new semantic detail.

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 states a specific verb and resource ('Get one stored Steam review') and disambiguates from the plural/search sibling by naming datasets_steam_reviews_search as the source of the identifiers. An agent can immediately tell this is a single-record lookup, not a listing.

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?

It implies the correct workflow by saying the ids come from datasets_steam_reviews_search, which is genuine when-to-use guidance. It stops short of stating what to do when an id is unknown or invalid, and names no explicit alternative for browsing reviews.

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

Deploy Server