Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_articles

Browse GosuGamers news and features archive in reverse chronological order, filtering by section or article type and paging through results to retrieve metadata and IDs for full-text access.

Instructions

GosuGamers news and features archive. Pages the GosuGamers news and features archive (51,051 articles), newest first, with optional section and type filters: id, type, title, teaser, section, publish time, author, image and URL. section is one of the 15 sections that carry articles (the six esports titles, Wild Rift, Free Fire, Battlegrounds Mobile India and the editorial sections entertainment, genshin-impact, honkai-star-rail, zenless-zone-zero, honor-of-kings and umamusume-pretty-derby); an article can belong to several sections. type is news or features. Paged with page and page_size (up to 100). Use gosugamers-article with a returned id for the text.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page; defaults to 1
typeNoArticle type; one of news, features; omit for both
sectionNoArticle section; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india, entertainment, genshin-impact, honkai-star-rail, zenless-zone-zero, honor-of-kings, umamusume-pretty-derby; omit for all
page_sizeNoPage size, 1 to 100; defaults to 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses ordering (newest first), archive size (51,051), pagination limits, return fields, and that an article can belong to multiple sections. It does not state auth/rate-limit requirements or explicitly note read-only/no-side-effect behavior, so it is strong but not exhaustive.

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?

The purpose and use case are front-loaded, and each major clause covers ordering, filters, paging, or the full-text alternative. However, it repeats the entire section enum from the schema and is dense, so trimming the redundant enum list would improve it.

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 four-parameter listing tool with no output schema and no annotations, the description supplies return fields, ordering, archive size, filter semantics, pagination, and the full-text follow-up. Nothing essential for calling it correctly appears 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; the description adds semantic context by grouping the 15 section enum values into esports and editorial categories and warning that an article can belong to several sections. It also maps type to news/features and page/page_size to paging, though defaults remain in the schema.

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 first sentence states a specific verb and resource: 'Pages the GosuGamers news and features archive.' It also lists the returned fields and explicitly distinguishes metadata listing from full-text retrieval by pointing to gosugamers-article, so an agent can select it over siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains that section and type filters are optional, that results are newest first, and that page/page_size paginate up to 100. It also routes full-text needs to gosugamers-article with a returned id, giving an explicit alternative condition.

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