Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_search_results

Search the Steam store by term, then page and sort results to retrieve appid, title, release date, review summary, price, and platforms as JSON.

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. Credential-free public Steam storefront JSON.

Input Schema

TableJSON 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?

No annotations are provided, so the description is the sole carrier of behavioral context. It adds that the API is 'credential-free public Steam storefront JSON,' which is useful for safety. However, it does not disclose rate limits, error behavior, or Read-only status, leaving some gaps for a public API.

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 three sentences long, front-loads the main purpose, and avoids filler. It is efficient and well-structured, though the word 'faceted' adds slight ambiguity without further explanation.

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

Completeness3/5

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

For a tool with no output schema, the description lists the returned fields, which helps agents understand the response shape. It also notes the credential-free nature. However, it does not cover default values for optional parameters (l, cc, start, count), how facets apply, or mention the sibling steam_search for comparison.

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 mentions 'start/count paging and sort_by,' which reinforces the schema but adds little new meaning such as examples, defaults, or relationships. The term 'faceted' is not backed by any facet parameters in the schema, creating minor ambiguity.

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 states a specific verb ('search'), resource ('Steam store'), and key capabilities (faceted, paginated, sortable), and lists the returned fields (appid, title, release date, review summary, price, platforms). It clearly conveys what the tool does, though it does not explicitly differentiate itself from the sibling steam_search tool.

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 over alternatives like steam_search. It mentions pagination and sorting but gives no exclusions, prerequisites, or comparison to other Steam-related tools. An agent must infer usage solely from the feature list.

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