Crawlora MCP

steam_category

Read-only

Fetch Steam catalog item records for a community-tag/category slug, with weighted tags and store facets such as platform, price, and specials. This is taxonomy/facet browsing, not free-text search. Use steam_tags or steam_tags_list to discover tags, steam_search for title typeahead, or steam_featured_categories for featured departments.

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": {
      "slug": "<slug>",
      "free": "<free>",
      "released_only": "<released_only>",
      "coming_soon_only": "<coming_soon_only>",
      "start": "<start>",
      "count": "<count>",
      "cc": "<cc>",
      "l": "<l>"
    },
    "name": "steam_category"
  }
}

Input Schema

Name	Required	Description
`l`	Yes	Steam store language name
`cc`	Yes	Store country code (ISO, selects currency)
`free`	Yes	Only free titles
`slug`	Yes	Community tag id (numeric) or tag name slug
`count`	Yes	Results per page (max 100)
`start`	Yes	Result offset for pagination
`released_only`	Yes	Only already-released titles
`coming_soon_only`	Yes	Only unreleased / coming-soon titles

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.

Changed8 schema fields changedOct 7, 2026
- addedInput schema / properties / cc / description
```
Added value: +"Store country code (ISO, selects currency)"
```
- addedInput schema / properties / coming_soon_only / description
```
Added value: +"Only unreleased / coming-soon titles"
```
- addedInput schema / properties / count / description
```
Added value: +"Results per page (max 100)"
```
- addedInput schema / properties / free / description
```
Added value: +"Only free titles"
```
- addedInput schema / properties / l / description
```
Added value: +"Steam store language name"
```
- addedInput schema / properties / released_only / description
```
Added value: +"Only already-released titles"
```
- addedInput schema / properties / slug / description
```
Added value: +"Community tag id (numeric) or tag name slug"
```
- addedInput schema / properties / start / description
```
Added value: +"Result offset for pagination"
```
First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description usefully discloses what the call returns - weighted tags plus store facets (platform, price, specials) - which is behavioral context beyond the annotations. It stops short of noting the all-params-required invocation shape or pagination behavior.

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 sentences, front-loaded with the core action before the routing guidance. Every sentence carries distinct information - what it fetches, what it returns, and which siblings to use instead - with no filler.

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?

An output schema exists (so return values need no prose), annotations carry the safety profile, and the schema fully documents parameters. The description supplies the one thing structured data cannot: the routing decision among the populous steam_* family. Nothing an agent needs to call this 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% across all 8 parameters, so the schema already documents slug, free, released_only, coming_soon_only, cc, l, start, and count. The description only loosely alludes to the facet dimensions (platform, price, specials) and adds no syntax or format detail beyond the schema, so the baseline of 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 catalog item records for a community-tag/category slug), and explicitly distinguishes itself from sibling tools by naming steam_tags, steam_tags_list, steam_search, and steam_featured_categories. An agent can tell this apart from other Steam tools without opening any 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?

Explicitly frames the use case: 'This is taxonomy/facet browsing, not free-text search,' then routes to the correct alternative for each neighboring need (tag discovery, title typeahead, featured departments). Both when-to-use and when-not-to-use are stated with the alternative tools named.

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.