Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_news_search

Search the steam-news dataset. Searches Steam news + announcements for tracked apps (one document per appid × gid; the latest items per app are kept). Filter by app_id for a single game's news, or full-text q over the title + contents.

Instructions

Search the steam-news dataset. Searches Steam news + announcements for tracked apps (one document per appid × gid; the latest items per app are kept). Filter by app_id for a single game's news, or full-text q over the title + contents. Sort enum: date_desc (newest first, default), date_asc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query over the news title + contents, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: date_desc, date_asc
app_idNoExact Steam app id filter
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "date_desc",
+  "date_asc"
+]
  2. Added
  3. Removedv1.6.0
  4. 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, the description carries the full burden and does well: it discloses the billing model (1 credit per record, minimum 2, 100 for a full page), which is critical and not in the schema. It also explains the dataset's retention behavior ('the latest items per app are kept'). It omits auth/permission needs and pagination limits beyond the schema, but the billing and retention context is genuinely valuable.

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?

Front-loads the purpose, then query modes, then sort, then billing. Every sentence is informative with little waste. The billing sentence is long but earns its place by quantifying cost implications.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no output schema and no annotations, the description supplies the dataset grain, the two query strategies, the sort default, and the cost model — enough for an agent to invoke it correctly and predict cost. Nothing essential is missing.

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 real meaning: it states the `sort` default (date_desc, newest first) which the schema does not, and clarifies that `app_id` scopes to a single game's news and `q` searches title+contents. It stops short of explaining page/page_size interaction beyond billing.

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?

States a specific verb (Search) and resource (the steam-news dataset: Steam news + announcements for tracked apps), and describes the document grain (one doc per appid × gid). This clearly separates it from the many sibling steam datasets (games, reviews, prices, charts).

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?

Gives two usage modes — filter by `app_id` for a single game's news, or full-text `q` over title+contents — which implies when each is appropriate. However, it never states when to prefer this tool over alternatives or any exclusions, so guidance is present but only implicit.

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