Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_community_recommendations

Fetch Steam store community-recommended reviews with author, playtime, helpful votes, and app details. Filter by review kind, playtime range, language, and region.

Instructions

Get the store's community-recommended reviews feed. Returns a batch of recent, quality user reviews recommended across the whole store (author, playtime, helpful votes, and the recommended app). Filter by review kind/sort, reviewer playtime window, review language, and store region. The upstream serves a fixed batch and, unauthenticated, does not support tag filtering or deep pagination. Credential-free public Steam storefront JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
playtime_maxNoMaximum reviewer playtime in hours (0 = no maximum)
playtime_minNoMinimum reviewer playtime in hours (0 = no minimum)
review_filterNoReview kind / sort
review_languageNoReview language: 'my_languages' or a Steam language name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / review_filter / enum
      Added value: +[
+  "helpful",
+  "recent",
+  "funny"
+]
  2. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It successfully discloses that the tool is credential-free, serves a fixed batch, does not support deep pagination or tag filtering, and returns public storefront JSON. It stops short of describing rate limits or the exact JSON response structure, but for a read-only fetch tool this is substantial transparency.

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

Conciseness5/5

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

Four dense sentences, each with a distinct purpose: what the tool does, what it returns, what filters exist, and what limitations apply. There is no filler, and the most important scoping information ('across the whole store') is front-loaded in the first sentence.

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 6-parameter tool with no output schema and no annotations, this description covers scope, return contents, filters, auth posture, and limitations. It doesn't specify batch size or the exact shape of the JSON response, but the 'fixed batch' disclosure and data-format mention reduce the impact of that gap.

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 baseline is 3. The description groups the parameters into categories ('review kind/sort, reviewer playtime window, review language, and store region') that map cleanly to the schema, but it adds no new meaning beyond what each parameter's description already states.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Get the store's community-recommended reviews feed.' It further clarifies scope ('across the whole store') and content ('author, playtime, helpful votes, and the recommended app'), making it readily distinguishable from other Steam tools like steam_top_sellers or steam_reviews_histogram.

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

Usage Guidelines4/5

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

The description establishes clear context: this is a store-wide feed of community-recommended reviews, with explicit filters and notable limitations (no tag filtering, no deep pagination). It does not name alternative tools or give explicit when-not-to-use conditions, but the context is strong enough that an agent can infer appropriate usage.

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