Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ign_headlines

Fetch current IGN headlines for a selected section, such as news, reviews, games, or tech. Returns titles, URLs, summaries, authors, and images when available.

Instructions

Get IGN section headlines. Returns current IGN headlines for one section. section is required and takes one of news, reviews, games, movies, tv, tech, nintendo, playstation, xbox, pc, mobile or comics. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesIGN 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?

No annotations are provided, so the description carries the burden. It usefully discloses the return shape (title, URL, summary, author, publication time, image) and notes fields are conditional ('when the outlet provides them'), but says nothing about freshness, pagination, rate limits, or auth, which matters for a live-feed tool.

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 short, front-loaded sentences: purpose first, then the required parameter, then return contents. The enum re-listing is mildly redundant with the schema but serves as a quick reference; overall it is tight and well-ordered.

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-parameter, no-output-schema read tool with no annotations, the description covers purpose, the required argument, and the fields returned. It is largely complete, with only minor gaps around freshness/pagination that an agent could not derive from structured fields.

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 coverage is 100% with the enum fully documented in the schema itself, so the schema already does the heavy lifting. The description only restates the allowed section values without adding format or behavioral meaning beyond the enum, matching the baseline 3.

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 IGN section headlines. Returns current IGN headlines for one section'), so an agent immediately knows what it does. It is scoped to a single section, but it never distinguishes itself from close siblings like ign_news or ign_sections, leaving some ambiguity in a large news-tool family.

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?

Usage is only implied: the tool returns headlines for one section, which suggests when it fits, but there is no explicit 'use this when...' or reference to alternatives such as ign_news vs ign_headlines vs ign_sections. The agent must infer routing from the purpose alone.

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