Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_games_search

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.

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, mostly_positive, mixed, mostly_negative, negative, very_negative, overwhelmingly_negative, insufficient. Sort enum: relevance, owners_desc, reviews_desc, review_score_desc, ccu_desc, metacritic_desc, price_asc, price_desc, release_desc, release_asc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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, mostly_positive, mixed, mostly_negative, negative, very_negative, overwhelmingly_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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / price_tier / enum
      Added value: +[
+  "free",
+  "under5",
+  "5to15",
+  "15to30",
+  "30to60",
+  "over60"
+]
    • addedInput schema / properties / review_tier / enum
      Added value: +[
+  "overwhelmingly_positive",
+  "very_positive",
+  "positive",
+  "mostly_positive",
+  "mixed",
+  "mostly_negative",
+  "negative",
+  "very_negative",
+  "overwhelmingly_negative",
+  "insufficient"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "owners_desc",
+  "reviews_desc",
+  "review_score_desc",
+  "ccu_desc",
+  "metacritic_desc",
+  "price_asc",
+  "price_desc",
+  "release_desc",
+  "release_asc"
+]
  2. Added
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: the credit-cost model (1 credit per record, minimum 2, a full 100-result page costs 100). That is valuable beyond the schema. However, it says nothing about auth requirements, what fields the returned records contain, or the pagination ceiling (which lives only in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose statement and billing note are front-loaded and earn their place, but the three inline enum listings are pure duplication of what the schema already declares, padding the description without adding information. Removing them would sharpen the definition.

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?

For a 29-parameter search with a fully documented schema and no output schema, the description is reasonably complete: it establishes scope and adds the non-obvious billing constraint. It stops short of explaining return shape or pagination limits, but the rich schema covers the parameter surface adequately.

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 the schema already documents all 29 parameters, including the three enums. The description re-lists the price_tier, review_tier, and sort enums verbatim, which duplicates rather than adds meaning. This lands on the baseline 3 where the schema does the heavy lifting.

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?

States a specific verb and resource: 'Search the Steam games dataset' and clarifies it queries 'enriched public Steam catalog records stored in a search index.' This is distinguishable from a generic search, but the description never names or contrasts the obvious siblings (datasets_steam_games_facets for faceting, datasets_steam_games_item for single-record lookup), so an agent must infer the boundary.

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 explains what the tool does but offers no when-to-use guidance, prerequisites, or alternatives. It does not tell the agent when to reach for this vs. datasets_steam_games_item or the facets tool, which is exactly the routing decision facing an agent in this large sibling set.

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

Deploy Server

Other Tools