Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_search_results

Query Steam store search results with pagination and sorting to retrieve app IDs, titles, release dates, review summaries, prices, and platform support.

Instructions

Faceted, paginated Steam store search. Runs the Steam store search with pagination and sorting and returns the result rows (appid, title, release date, review summary, price, platforms). Supports start/count paging and sort_by.

Input Schema

NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
termYesSearch term
countNoResults per page (max 100)
startNoResult offset for pagination
sort_byNoSort order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort_by / enum
      Added value: +[
+  "Relevance",
+  "Released_DESC",
+  "Name_ASC",
+  "Price_ASC",
+  "Price_DESC",
+  "Reviews_DESC"
+]
  2. 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. It usefully discloses the return shape (since there is no output schema) and that paging/sorting are supported, but says nothing about rate limits, currency/locale effects, defaults, or failure behavior for a store-backed search.

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?

Two tight sentences that front-load the core purpose, then the return fields. Minor redundancy between 'Faceted, paginated' and 'with pagination and sorting', but no padding.

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?

There is no output schema, and the description compensates by listing the returned fields and paging behavior, which is the key missing information for this tool. The remaining gap is the lack of differentiation from steam_search and any locale/currency caveats.

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 every parameter (l, cc, term, count, start, sort_by) is already documented in the schema. The description only echoes 'start/count paging and sort_by' without adding syntax, defaults, or interaction details, so baseline 3 applies.

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 ('Runs the Steam store search') and even enumerates the returned row fields (appid, title, release date, review summary, price, platforms). It does not, however, distinguish itself from the sibling steam_search, so an agent cannot tell from the description alone which of the two overlapping tools to pick.

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 gives no when-to-use guidance, no prerequisites, and no comparison to the clearly overlapping steam_search sibling. It only states capability, leaving the selection decision entirely to the agent.

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