Crawlora MCP

steam_community_recommendations

Read-only

List recent user reviews recommended across the Steam store, including the app, author, playtime, and helpful votes. Filter by review kind, playtime window, language, or store region. The source supplies a fixed batch with no tag filter or deep pagination. Use steam_reviews for one app's reviews.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "steam_community_recommendations"
  }
}

Input Schema

Name	Required	Description
`l`	No	Language code
`cc`	No	Store country code (ISO, selects currency)
`playtime_max`	No	Maximum reviewer playtime in hours (0 = no maximum)
`playtime_min`	No	Minimum reviewer playtime in hours (0 = no minimum)
`review_filter`	No	Review kind / sort. Documented values: helpful, recent, funny.
`review_language`	No	Review language: 'my_languages' or a Steam language name

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.

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / cc / description

Added value: +"Store country code (ISO, selects currency)"

addedInput schema / properties / l / description
```
Added value: +"Language code"
```

addedInput schema / properties / playtime_max / description

Added value: +"Maximum reviewer playtime in hours (0 = no maximum)"

addedInput schema / properties / playtime_min / description

Added value: +"Minimum reviewer playtime in hours (0 = no minimum)"

addedInput schema / properties / review_filter / description

Added value: +"Review kind / sort. Documented values: helpful, recent, funny."

addedInput schema / properties / review_language / description

Added value: +"Review language: 'my_languages' or a Steam language name"

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the read-only/open-world safety profile, and the description adds real behavioral context: the source returns a fixed batch with no tag filtering or deep pagination. That's a meaningful constraint an agent couldn't infer from annotations alone, though rate limits and result volume are unstated.

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?

Four tight sentences, front-loaded with purpose and return contents, then filters, then the source's limitations, then the sibling routing. Dense and largely waste-free, though the field enumeration in sentence one is slightly list-like.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. The description still covers scope, filter dimensions, the fixed-batch limitation, and sibling routing, leaving only modest gaps such as result-size expectations.

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 description coverage is 100%, so all six parameters are already documented; the baseline of 3 applies. The description groups them into filter categories (review kind, playtime window, language, region), adding modest organizational value but no new syntax or semantics.

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 ('List recent user reviews recommended across the Steam store') plus the payload fields returned. It also explicitly contrasts scope with the sibling steam_reviews ('one app's reviews'), so an agent can differentiate without opening either schema.

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 names the alternative (steam_reviews) and the condition selecting it (single-app reviews), which gives clear routing. It falls short of 5 because it doesn't state other when-not conditions (e.g. that per-app analytics or histogram data live in other siblings).

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.

Resources

Need Help?