Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

datasets_steam_news_item

Retrieve a single Steam announcement by app_id and gid to inspect the full details of a news item found in search results.

Instructions

Get one stored Steam news item. Retrieves one Steam announcement by the appid and gid fields returned by datasets_steam_news_search.

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": {
      "app_id": "<app_id>",
      "gid": "<gid>"
    },
    "name": "datasets_steam_news_item"
  }
}

Input Schema

Name	Required	Description	Default
`gid`	Yes	Steam news gid
`app_id`	Yes	Steam app id

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are supplied, so the description needs to carry the behavioral burden. The word "stored" hints that this is a cached read rather than a live fetch, but the description does not say what happens when the gid or app_id is not found, or whether an error or an empty result is returned.

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?

Two sentences with no waste: the resource being fetched is stated first, then the provenance of the identifiers. Every sentence is useful.

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 tool with two required parameters, the description is nearly sufficient. It could note what fields a returned announcement contains, since there is no output schema. Calling it a "Steam announcement" gives some idea of the response, so this is a minor 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 both parameters already have descriptions, which sets the baseline at 3. The description does usefully point to where the identifier values come from, but it refers to `appid` while the schema names the field `app_id`, which is a small inconsistency that reduces the added clarity.

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 names a specific verb and resource ("Get one stored Steam news item", "Retrieves one Steam announcement") and uses the singular "one" to contrast with the sibling search tool, so an agent can distinguish it from datasets_steam_news_search without opening either schema.

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?

It states the precondition clearly by saying the `appid` and `gid` fields come from `datasets_steam_news_search`, giving the agent a clear path to use after a search. There is no explicit exclusion, but for a detail-fetch tool, the only real alternative is the search sibling, and that is named.

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

Deploy Server