Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bo3_news_feed

Fetch BO3.gg editorial feeds by game, section, locale, category, tag, or sort with paging to browse news, articles, wiki, predictions, and reviews.

Instructions

BO3.gg news, articles, wiki and predictions feed. Returns BO3.gg's editorial feed for one game with paging and filters: section (news, article, wiki, predictions, reviews), a locale (16 languages, en by default), a category 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 canonical URL; total and has_more page through the archive (over 100,000 items across games).

Input Schema

NameRequiredDescriptionDefault
tagNoTag slug such as team-liquid or pgl-masters-bucharest-2026 (team, player, tournament or topic tag); an unknown tag returns an empty list
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb, games (general gaming news); defaults to cs2
sortNoOrder by publish time; one of newest, oldest; defaults to newest
limitNoPage size, 1 to 100; defaults to 20
localeNoLanguage of the items; one of en, ru, pt, es, de, fr, tr, pl, id, vi, ja, ko, ua, ms, tl, da; defaults to en
offsetNoZero-based offset; defaults to 0
sectionNoEditorial section; one of news, article, wiki, predictions, reviews (game reviews, game=games only); defaults to news
categoryNoCategory id from bo3-news-categories, for example 38 (Predictions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/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 pagination mechanics (up to 100 per page, `total` and `has_more` to walk the archive), the archive scale (100,000+ items), defaults (locale en, section news, game cs2), and the shape of each returned item. It omits any statement about rate limits, ordering stability across pages, or locale fallback behavior for a read feed this large.

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, front-loaded with what the feed is, then the filter surface, then the item shape and paging fields. Nothing is redundant and nothing is buried.

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 an 8-optional-parameter list tool with no output schema, the description supplies the item field list and the paging fields (`total`, `has_more`), which the agent would otherwise have to discover empirically. What remains uncovered is combination/edge behavior — how tag + category + section interact and what an unknown category yields — which the schema only partially addresses for tags.

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 applies: every parameter including tag, game, offset and category already has an enum or explanatory text in the schema. The description restates section/locale/sort/limit and 'for one game' but adds no filtering-combination semantics (e.g. whether tag, category and section compose) beyond what the schema says.

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: "Returns BO3.gg's editorial feed for one game with paging and filters", and enumerates the sections it spans (news, article, wiki, predictions, reviews). The word "editorial" implicitly separates it from the forum-style siblings (bo3_forum), and it names bo3-news-categories as the source of category ids, but it never explicitly contrasts itself with those siblings.

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 establishes the context of use (one game's editorial feed, filterable by section/locale/category/sort) and points to bo3_news_categories as the prerequisite for the category id. It stops short of stating when to prefer this over bo3_forum or another outlet's news feed, so there are no explicit exclusions.

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