Crawlora MCP

steam_search_results

Read-only

Fetch paginated and sorted Steam store-search result rows for term, including app ID, title, date, review summary, price, and platforms. Use steam_search for quick typeahead or steam_app for one game's details.

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": {
      "term": "<term>"
    },
    "name": "steam_search_results"
  }
}

Input Schema

Name	Required	Description
`l`	No	Language code
`cc`	No	Store country code (ISO, selects currency)
`term`	Yes	Search term
`count`	No	Results per page (max 100)
`start`	No	Result offset for pagination
`sort_by`	No	Sort order. Documented values: Relevance, Released_DESC, Name_ASC, Price_ASC, Price_DESC, Reviews_DESC.

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 / count / description
```
Added value: +"Results per page (max 100)"
```
- addedInput schema / properties / l / description
```
Added value: +"Language code"
```
- addedInput schema / properties / sort_by / description
```
Added value: +"Sort order. Documented values: Relevance, Released_DESC, Name_ASC, Price_ASC, Price_DESC, Reviews_DESC."
```
- addedInput schema / properties / start / description
```
Added value: +"Result offset for pagination"
```
- addedInput schema / properties / term / description
```
Added value: +"Search term"
```
First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context beyond that — it is paginated and sorted — but does not cover rate limits, auth needs, or result-set size, and its field list partly overlaps the output schema.

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?

Two tight sentences, zero filler, with the core fetch behavior front-loaded and the sibling routing appended where it belongs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety, a full output schema, and 100% parameter coverage, the description supplies everything an agent still needs: purpose, scope, and sibling routing. Nothing required to invoke it correctly is missing.

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 pagination (start/count), language, country, and sort_by are already documented. The description only echoes 'paginated and sorted' and the `term` parameter, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 ('Fetch') and resource (Steam store-search result rows) scoped to `term`, and lists the fields returned. It explicitly distinguishes itself from siblings, so an agent can tell it apart from steam_search or steam_app without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names two alternatives with the exact condition that selects each: steam_search for quick typeahead, steam_app for one game's details. Nothing about when to pick this tool over its siblings is left to inference.

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?