Crawlora MCP

steam_news

Read-only

Fetch recent Steam news items for one app, including announcement titles, authors, and post contents. Use the numeric appid; count limits items to 50 and maxlength caps each body at 300 characters by default or returns full content with -1.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appid": "<appid>"
    },
    "name": "steam_news"
  }
}

Input Schema

Name	Required	Description
`appid`	Yes	Numeric Steam app id
`count`	No	Number of posts (max 50)
`maxlength`	No	Max characters of each post body; default 300, set -1 for full content

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / appid / description
```
Added value: +"Numeric Steam app id"
```
- addedInput schema / properties / count / description
```
Added value: +"Number of posts (max 50)"
```
- addedInput schema / properties / maxlength / description
```
Added value: +"Max characters of each post body; default 300, set -1 for full content"
```
First observedOct 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the count cap and body-truncation default, but those details are also present in the schema, and it says nothing about pagination, freshness of 'recent', or rate limits.

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 compact sentences with the core purpose front-loaded and no wasted words. The second sentence largely restates schema-level parameter details, which slightly dilutes it, but overall it is tight and well ordered.

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 simple one-required-parameter read tool with an output schema, the description covers purpose, the key parameters, and what is returned. Nothing critical is missing, though it does not clarify recency semantics or result ordering.

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 restates the count max (50) and maxlength default (300)/-1 behavior, which the schema already documents, and adds no format or syntax detail beyond that.

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 ('Fetch recent Steam news items for one app') and enumerates what is returned (titles, authors, post contents). It is clearly distinguishable from siblings like steam_reviews or steam_app, though it does not explicitly name or contrast any alternative.

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 note 'Use the numeric appid' is the only usage guidance; there is no statement of when to prefer this tool over siblings such as datasets_steam_news_search, nor any prerequisites or exclusions. Usage is implied by the resource description rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.