Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_news

Fetch recent news and announcement posts for any Steam app by its numeric appid. Control the number of posts and truncate post bodies as needed.

Instructions

Get recent news posts for a Steam app. Returns recent news and announcement posts for a Steam app by numeric appid (for example 570). count sets the number of posts (default 10, max 50) and maxlength caps each post body in characters (default 300, -1 for the full body). Each post has gid, title, URL, author, contents, feed label and name, date, is_external_url and tags.

Input Schema

NameRequiredDescriptionDefault
appidYesNumeric Steam app id
countNoNumber of posts (max 50)
maxlengthNoMax characters of each post body; default 300, set -1 for full content

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 disclosure burden. It implies a read operation ('Get') and usefully enumerates the returned fields (gid, title, URL, author, contents, date, is_external_url, tags), but says nothing about rate limits, auth requirements, or pagination behavior. Adequate but with clear gaps for a no-annotation 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?

Two tight sentences: purpose first, then parameters and return shape. Very little waste, though the return-field enumeration is somewhat long.

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 output schema, the description compensates by listing the returned post fields, and it documents all three parameters. For a simple read-only fetch it is nearly complete; only the absence of any usage/routing guidance keeps it from the top.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds value the schema omits: the default count of 10 (schema only states 'max 50'), the appid example '570', and confirmation that maxlength caps the post body. This exceeds the baseline for a well-documented schema.

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 (Get) and resource (recent news posts for a Steam app) scoped to a numeric appid, which is clear and actionable. It does not explicitly differentiate from other steam_* siblings (steam_app, steam_reviews, steam_featured), so it stops short of the top band.

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?

There is no guidance on when to use this tool versus alternatives, and no exclusions or prerequisites. The agent is left to infer that this is the app-specific news feed.

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