Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

globalnews_headlines

Fetch recent Global News headlines for a specified section slug, such as world or toronto, and return each item's title, URL, summary, author, publication time, and image when available.

Instructions

Get Global News section headlines. Returns recent Global News headlines for one section. section is required and takes a slug such as canada, world, money, us-news, the-curator or a local-station slug like toronto or calgary. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesGlobal News RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/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 does usefully disclose the return shape (title, URL, summary, author, publication time, image) and notes fields are conditional ("when the outlet provides them"), which helps an agent handle missing data. It says nothing about rate limits, auth, pagination, or result counts, so it is only partially complete for an unannotated 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 tight sentences, front-loaded with the core action, then parameter guidance, then return shape. No filler, though the return-shape sentence partially overlaps what the input schema already implies about a section feed.

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?

With one required enum parameter, no annotations, and no output schema, the description covers the essential call contract: what section to pass and what each returned item contains. Gaps are minor (no pagination/volume expectations, no sibling routing), so it is largely complete for a simple feed tool.

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% with an enum, so the baseline is 3. The description goes beyond the enum by explaining the slug taxonomy, i.e. that values span national/vertical slugs (`canada`, `world`, `money`, `us-news`, `the-curator`) and local-station slugs (`toronto`, `calgary`), which adds real selection guidance not present in the schema.

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 Global News section headlines") and scopes it to one section, which differentiates it from a general per-outlet news feed. It does not explicitly name or contrast with its closest siblings like globalnews_news or globalnews_sections, so an agent must infer the split.

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?

The required `section` parameter and its slug examples imply use, and the description is clear that a section must be chosen. However, it never states when to pick this tool over globalnews_news, globalnews_sections, or globalnews_article, so routing to the right sibling is left to inference.

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