Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_items

Batch-resolve up to 100 Steam app IDs into store items with weighted community tags, review-score breakdown, credits, release date, platforms, and price.

Instructions

Resolve a batch of app ids to store items with weighted tags. Resolves up to 100 Steam app ids in one call to store items, each carrying its WEIGHTED community tags, review-score breakdown, developer/publisher credits, release date, platforms and price. The batch enrichment primitive for the community-tag taxonomy.

Input Schema

NameRequiredDescriptionDefault
lNoSteam store language name
ccNoStore country code (ISO, selects currency)
appidsYesComma-separated numeric app ids (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does useful work by disclosing the 100-id batch cap and enumerating the returned payload (weighted tags, review-score breakdown, credits, release date, platforms, price). It omits auth/rate-limit behavior, error handling for invalid ids, and whether a partial failure aborts the batch.

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 is front-loaded, but the first two sentences restate the same action ('Resolve a batch of app ids to store items' / 'Resolves up to 100 Steam app ids in one call to store items'), which is redundant. The closing line is marketing framing rather than actionable information.

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?

With no annotations and no output schema, the description fills the key gap by enumerating return fields and the batch ceiling, which is enough for an agent to invoke it correctly. Only edge-case behavior (invalid ids, partial failures) is left unstated.

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 three parameters. The description only restates the max-100 constraint that the schema already carries and adds nothing about the l (language) or cc (currency) parameters, so baseline 3 is correct.

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 ('Resolve') and resource ('a batch of app ids to store items'), and the 'batch / up to 100' framing distinguishes it from single-item siblings like steam_app. However, it never names a sibling or explicitly contrasts its scope with steam_tags or steam_reviews, so differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

The 'batch enrichment primitive' framing implies when it is appropriate (bulk app-id resolution), but there is no explicit when-to-use/when-not guidance and no alternative tool is named. An agent must infer that this replaces N calls to a single-app sibling.

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