Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

steam_reviews

Fetch Steam app user reviews with cursor pagination and aggregate sentiment totals. Filter by language, sentiment, and purchase type.

Instructions

List reviews for a Steam app. Returns a page of user reviews for an app with cursor pagination and an aggregate query_summary (score, positive/negative totals). Aggregate totals populate only on the first page (cursor=*). Pass the returned cursor back to page. Credential-free public Steam storefront JSON.

Input Schema

TableJSON Schema

Name	Required	Description
`appid`	Yes	Numeric Steam app id
`cursor`	No	Pagination cursor from the previous page
`filter`	No	Sort order
`language`	No	Steam language name or 'all'
`day_range`	No	Look-back window in days (filter=all only, max 365)
`review_type`	No	Review sentiment filter
`num_per_page`	No	Reviews per page (max 100)
`purchase_type`	No	Purchase source filter

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.17.5Sep 26, 2026
- addedInput schema / properties / filter / enum
```
Added value: +[
+  "recent",
+  "updated",
+  "all"
+]
```
- addedInput schema / properties / purchase_type / enum
```
Added value: +[
+  "all",
+  "steam",
+  "non_steam_purchase"
+]
```
- addedInput schema / properties / review_type / enum
```
Added value: +[
+  "all",
+  "positive",
+  "negative"
+]
```
Addedv1.5.0Jul 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and handles it well. It explicitly discloses credential-free public access, page-based cursor pagination, and the non-obvious behavior that aggregate totals populate only on the first page via cursor=*. These are exactly the behavioral details an agent needs before calling the tool.

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 tightly packed sentences with no filler. The core purpose is front-loaded, and every additional sentence adds needed operational detail: pagination, query_summary behavior, and authentication requirements.

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 an 8-parameter tool with no annotations and no output schema, the description covers the critical context: what it returns, how pagination works, and that no credentials are needed. It does not enumerate exact response fields or error behavior, but the schema already documents parameters fully and the main agent-facing risks are addressed.

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%, so the baseline is 3. The description adds meaningful value beyond the schema by explaining the special initial cursor value (cursor=*) and instructing the agent to pass the returned cursor back to page. This clarifies pagination semantics that the bare parameter names do not convey.

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 opens with a specific verb and resource: 'List reviews for a Steam app.' It adds that these are user reviews with cursor pagination and an aggregate query_summary, which separates this tool from nearby Steam siblings like steam_reviews_histogram or steam_community_recommendations. The purpose is unambiguous.

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 makes the usage context clear: list a page of user reviews for a Steam app, pass the returned cursor back to paginate, and expect query_summary totals only on the first page. It does not explicitly name alternative tools or exclusion conditions, but the invocation workflow is well stated.

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

Deploy Server

steam_reviews

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools