Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

euronews_sections

List 42 Euronews English-edition sections with slugs, names, and URLs to identify valid categories for headline requests.

Instructions

Get Euronews sections. Lists the 42 Euronews English-edition sections accepted by euronews-headlines. Top-level themes include news, business, culture, earth, health, my-europe, next and travel, each with sub-sections such as news-africa or earth-climate. Each entry has the slug, name and url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exact cardinality (42 sections), the English-edition scope, the top-level themes and sub-section naming pattern, and the returned fields (slug, name, url). It does not mention auth or rate limits, but for a read-only enumeration tool this is a strong disclosure.

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?

Purpose is front-loaded in the first sentence, followed by scope, examples, and return shape. The example slugs (`news-africa`, `earth-climate`) are illustrative rather than padding. Slightly list-heavy but each sentence earns its place.

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 parameterless listing tool with no output schema, the description is complete: it explains what is returned (slug, name, url), how many entries exist, and how the values relate to the sibling headlines tool. Nothing an agent needs in order to call it correctly is 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?

There are zero input parameters, so the baseline of 4 applies. The description correctly adds context about the shape of the returned data (slug/name/url) rather than fabricating parameter semantics.

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?

States a specific verb and resource ("Get Euronews sections") and immediately ties the resource to its sibling by specifying these are "the 42 Euronews English-edition sections accepted by `euronews-headlines`." An agent can distinguish this from `euronews_headlines`, `euronews_news`, and other `*_sections` tools without opening any schema.

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

Usage Guidelines4/5

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

The description makes the primary use case clear: this enumerates the valid section values that `euronews-headlines` accepts, implying you resolve a section slug here before filtering headlines. It provides clear context but does not explicitly state when-not to use it or name alternative section sources.

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