Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_games_search

Search Steam game catalog records by title, developer, publisher, genre, tag, price, reviews, platform, and release year; sort and filter results.

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.

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, 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It mentions 'enriched public Steam catalog records stored in a search index' but doesn't disclose pagination limits, default sort order, result format, or that all parameters are optional. It lacks critical behavioral context for a search tool.

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 and starts with a clear purpose statement. However, it spends a significant portion listing enum values that are redundant with the schema. It could be more front-loaded with essential information, but it remains efficiently short.

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?

For a tool with 29 optional parameters and no output schema, the description is notably incomplete. It doesn't explain default behavior (e.g., default sort, default page size), result structure, or common usage patterns. The agent is left without sufficient context to effectively use 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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds little beyond repeating enum values (price_tier, review_tier, sort) that are already in the schema. It doesn't explain parameter interactions or provide examples, so baseline 3 is appropriate.

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 the tool's purpose: 'Search the Steam games dataset.' It identifies the verb and resource precisely. However, it doesn't differentiate from sibling tools like datasets_steam_games_facets or datasets_steam_games_item, relying on the name to disambiguate.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention when not to use it, exclusions, or how it differs from other Steam dataset tools. The description only states what it does, leaving the agent to infer usage context.

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