Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_steam_games_facets

Get aggregated counts of Steam games by facets like genre, price tier, review tier, and platform support. Filter by developer, publisher, tags, and more to analyze the dataset.

Instructions

Facet the Steam games dataset. Returns terms aggregation counts for the Steam games dataset. Facet enum: type, developer, publisher, genres, categories, price_tier, review_tier, owners_bucket, release_year, run_id, is_free, coming_soon, platform_windows, platform_mac, platform_linux. price_tier enum: free, under5, 5to15, 15to30, 30to60, over60. review_tier enum: overwhelmingly_positive, very_positive, positive, mixed, negative, insufficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over name, developer and publisher, max 256 characters
macNoFilter by macOS support
tagNoExact community-tag filter (e.g. Roguelike, Cozy), max 128 characters
typeNoExact storefront type filter, max 128 characters
facetYesFacet enum: type, developer, publisher, genres, categories, tags, primary_tag, price_tier, review_tier, owners_bucket, release_year, run_id, is_free, coming_soon, platform_windows, platform_mac, platform_linux
genreNoExact genre filter, max 128 characters
linuxNoFilter by Linux support
run_idNoExact crawl run-id filter, max 128 characters
is_freeNoFilter by free-to-play flag
min_ccuNoMinimum peak concurrent users yesterday
on_saleNoFilter by titles currently discounted (discount_pct > 0)
windowsNoFilter by Windows support
categoryNoExact store category filter, max 128 characters
developerNoExact developer filter, max 128 characters
publisherNoExact publisher filter, max 128 characters
min_ownersNoMinimum estimated owners (SteamSpy owners midpoint)
price_tierNoPrice-tier enum: free, under5, 5to15, 15to30, 30to60, over60
review_tierNoReview-tier enum: overwhelmingly_positive, very_positive, positive, mixed, negative, insufficient
min_positiveNoMinimum positive review count
owners_bucketNoExact SteamSpy owners-range bucket filter, max 128 characters
min_metacriticNoMinimum Metacritic score, 0 through 100
max_price_centsNoMaximum current price in cents
min_price_centsNoMinimum current price in cents
max_release_yearNoMaximum release year
min_release_yearNoMinimum release year
min_review_scoreNoMinimum positive-review ratio, 0 through 1
min_total_reviewsNoMinimum total review count
Behavior2/5

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

No annotations provided. The description implies a read operation but does not explicitly state it is read-only, mention rate limits, authentication needs, or how filters interact (e.g., AND/OR logic). The lack of behavioral detail is a significant gap for a tool with 27 parameters.

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?

The description is concise at two sentences. The first sentence captures the core purpose. The second sentence lists enums but is a bit dense; could be structured more cleanly. Still efficient and front-loaded.

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

Completeness2/5

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

No output schema is provided, and the description does not explain the output structure (e.g., format of aggregation counts, max results, sorting). For a complex facet tool with many filters, the missing output context reduces completeness.

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 the baseline is 3. The description adds the facet enum list and sub-enums for price_tier and review_tier, but these are already present in the schema's parameter descriptions. No additional semantic value beyond redundancy.

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 clearly states the tool facets the Steam games dataset and returns terms aggregation counts. It distinguishes itself from sibling tools like datasets_steam_games_search (search results) and datasets_steam_games_item (single item) by specifying the aggregation nature.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives. The implied usage is for getting aggregated counts per field, but no exclusions or context about when to prefer search or item tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server