Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

euronews_headlines

Retrieve Euronews English-edition headlines by section slug, such as business, culture, or travel, returning titles and URLs for monitoring current news topics.

Instructions

Get Euronews section headlines. Returns the latest Euronews English-edition headlines for one section. section is required and takes one of 42 slugs, including themes (business, culture, earth, health, next, travel) and their sub-sections such as business-markets or next-space. Each item has its title and URL; the news and business sections also carry summary and publication time.

Input Schema

NameRequiredDescriptionDefault
sectionYesEuronews section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 full burden. It usefully discloses the return content (title and URL per item, plus summary and publication time for news/business), but says nothing about read-vs-write nature, auth requirements, or rate limits.

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?

Three tight sentences, front-loaded with the core action, then parameter detail, then return shape. Every sentence adds information with no redundancy.

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 no output schema and no annotations, the description adequately covers what the tool returns and how to select a section. It is nearly complete for a simple read tool, missing only explicit sibling differentiation and any auth/limit context.

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% and the enum already lists all 42 slugs, so the baseline is 3. The description adds genuine meaning by grouping slugs into themes and sub-sections with examples, and by noting that only `news` and `business` sections return summary and publication time.

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 Euronews section headlines' and clarifies the scope is the latest English-edition headlines for a single section. Clear and precise, though it doesn't explicitly distinguish itself from adjacent siblings like euronews_news or euronews_sections.

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 description explains the required parameter and its valid values, which implies how to call it, but never states when to choose this tool over euronews_news, euronews_article, or euronews_sections. Usage is only implicitly conveyed.

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