Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_steam_games_search

Search Steam game catalog by name, genre, price, reviews, release year, and more. Filter by platform, discounts, and tags to find specific games.

Instructions

Search the Steam games dataset. Searches enriched public Steam catalog records stored in a search index. price_tier enum: free, under5, 5to15, 15to30, 30to60, over60. review_tier enum: overwhelmingly_positive, very_positive, positive, mixed, negative, insufficient. Sort enum: relevance, owners_desc, reviews_desc, review_score_desc, ccu_desc, metacritic_desc, price_asc, price_desc, release_desc, release_asc.

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, Metroidvania, Cozy), max 128 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, owners_desc, reviews_desc, review_score_desc, ccu_desc, metacritic_desc, price_asc, price_desc, release_desc, release_asc
typeNoExact storefront type filter (e.g. game, dlc, demo), max 128 characters
genreNoExact genre filter (e.g. Action, Indie), 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 (e.g. Single-player), max 128 characters
developerNoExact developer filter, max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
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 are provided, and the description only says 'Searches ... records stored in a search index', implying a read operation. It does not disclose pagination behavior, rate limits, authentication needs, or what happens with empty results. Listing enums is helpful but does not compensate for the lack of behavioral context.

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: one sentence defining the tool followed by three lines listing enums. It is front-loaded with the core purpose. There is no redundancy or fluff, though it could be slightly more structured.

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?

Given the tool has 29 parameters and high complexity, the description is minimal. It does not mention pagination (page, page_size), result format, or how filters interact. No output schema is provided, so the agent lacks information about what the response contains. Incomplete for such a complex search tool.

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?

The input schema has 29 parameters with 100% description coverage, so the schema already provides meaning. The description repeats enum values for price_tier, review_tier, and sort, but does not add new information beyond what is in the schema. No examples or explanations of parameter interactions are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search the Steam games dataset' and specifies it searches 'enriched public Steam catalog records', which aligns with the tool name. However, it does not explicitly differentiate from sibling search tools like datasets_steam_prices_search or datasets_steam_reviews_search, though the name and context imply it's for the games catalog.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no when-not-to-use conditions, and no exclusions. Sibling tools like datasets_steam_games_facets or datasets_steam_games_item exist, but the description does not help an agent choose between them.

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