Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kotaku_headlines

Fetch recent Kotaku headlines for a required section slug, such as news, reviews, games, or deals. Returns each article's title, URL, summary, author, publication time, and image.

Instructions

Get Kotaku section headlines. Returns recent Kotaku headlines for one section. section is required and takes one of 17 slugs such as news, reviews, games, game-tips, retro, horror or deals. Each item has its title, URL, summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesKotaku section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the return shape (title, URL, summary, author, publication time, image), which is genuinely useful for a read-only list tool, but says nothing about pagination, result limits, recency window, or ordering.

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?

Three sentences, front-loaded with the purpose before the parameter detail and the return fields. Little waste, though the slug examples partly duplicate the enum.

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 single-required-enum, no-output-schema read tool, the description covers the callable surface and the returned fields well. Remaining gaps (pagination, ordering, relationship to kotaku_news) are minor rather than blocking.

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% and the enum already lists all 17 valid slugs, so the schema does the heavy lifting. The description repeats a subset of those slugs rather than adding format or semantics beyond what the schema provides, so the baseline 3 is appropriate.

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 ('Get Kotaku section headlines') and clarifies scope ('for one section'). It never distinguishes this from the sibling kotaku_news or explains the relationship to kotaku_sections, which the 'headlines' family name alone can't resolve.

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?

States that section is required and lists example slugs, which implies how to call it, but gives no explicit when-to-use or when-not-to-use guidance relative to kotaku_news, kotaku_article, or kotaku_sections. Usage must be inferred from the name and the field enumeration.

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