Crawlora MCP

bo3_news_feed

Read-only

Returns BO3.gg's editorial feed for one game (cs2 by default; valorant, lol, dota2, r6siege, mlbb, or games for BO3's general gaming news) with paging and filters: section (news, article, wiki, predictions, reviews), locale (en, ru, pt, es, de, fr, tr, pl, id, vi, ja, ko, ua, ms, tl or da; default en), tag (a tag slug such as team-liquid, taken from the tags of any returned item), category (an id from bo3_news_categories) and sort (newest, oldest), up to 100 per page. Each item has slug, title, description, category, publish time, author, tags, image and URL; total and has_more page through the archive. Use it for match predictions, news and guides; use bo3_news_categories first to find a category id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bo3_news_feed"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Optional tag slug such as team-liquid or pgl-masters-bucharest-2026 (team, player, tournament and topic tags; take them from the tags of any returned item); only items with that tag are returned.
`game`	No	Optional game: cs2 (default), valorant, lol, dota2, r6siege, mlbb or games (BO3 general gaming news).
`sort`	No	Optional order: newest (default) or oldest.
`limit`	No	Optional page size 1 to 100, default 20.
`locale`	No	Optional language of the items: en (default), ru, pt, es, de, fr, tr, pl, id, vi, ja, ko, ua, ms, tl or da.
`offset`	No	Optional zero-based offset, default 0.
`section`	No	Optional section: news (default), article, wiki, predictions or reviews (game reviews, games only).
`category`	No	Optional category id from bo3_news_categories, for example 38 for Predictions.

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.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / tag

Added value: +{
+  "description": "Optional tag slug such as team-liquid or pgl-masters-bucharest-2026 (team, player, tournament and topic tags; take them from the tags of any returned item); only items with that tag are returned.",
+  "type": "string"
+}

AddedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuine behavior context: up to 100 items per page, 'total and has_more' for paging through the archive, and the exact fields each item exposes. It says nothing about rate limits, auth, or whether the archive is unbounded, which keeps it below a 5.

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?

A single dense paragraph that is front-loaded with the resource, default game, and paging model before filters, and closes with routing advice. It loses some efficiency by re-listing all 16 locale codes and 7 game scopes that the schema already enumerates verbatim.

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?

Eight optional parameters with full schema coverage and an output schema present means the structured data carries the return shape; the description still covers scope, defaults, paging model, and where category/tag values come from. Nothing an agent needs in order to call it correctly is missing.

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 every parameter including defaults, so a 3 baseline applies. The description largely restates the same enum lists (games, locales, sections) and the tag/category sourcing that the schema descriptions already carry, adding little new semantics.

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?

Opens with a specific verb and resource: 'Returns BO3.gg's editorial feed for one game', names the default (cs2) and the alternate game scopes. It is clearly distinguishable from sibling bo3_news_categories, which it explicitly routes to for category ids.

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?

Gives an explicit use case ('match predictions, news and guides') and a prerequisite chain ('use bo3_news_categories first to find a category id', plus 'tag ... taken from the tags of any returned item'). It stops short of stating when NOT to use it versus neighbours such as bo3_forum or bo3_match, so no exclusions are covered.

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.