Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

euronews_article

Fetch a Euronews English-edition article by URL and return its title, description, publish and update times, section, authors, lead image, and body paragraphs.

Instructions

Get Euronews article content. Returns one Euronews English-edition article by its url, in the form https://www.euronews.com/YYYY/MM/DD/<slug>. The response has the title, description, publish and update times, section, authors, lead image and body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Euronews article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden; it does so reasonably by enumerating the returned fields (title, description, publish/update times, section, authors, lead image, paragraphs) and disclosing the English-edition restriction. It stops short of covering error behavior or access constraints, but as an unannotated read tool it adds useful context.

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 short sentences, front-loaded with the purpose, then the required input form, then the return contents. No filler; every sentence adds information.

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?

With no output schema and no annotations, the description compensates by listing the response fields and the input format, which is everything an agent needs to call a single-article fetch correctly.

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 schema already labels the parameter as the canonical article URL, but the description adds real value by giving the concrete URL pattern with the YYYY/MM/DD/<slug> structure, which tells an agent what a valid input looks like.

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 (Get) and resource (Euronews article content), and explicit scope: one English-edition article identified by URL. This clearly separates it from siblings like euronews_headlines or euronews_news, which list rather than fetch a single article.

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 requirement that a URL be supplied in the form https://www.euronews.com/YYYY/MM/DD/<slug> implies the tool is a follow-up to a listing tool, but it never says so explicitly or names euronews_headlines/euronews_news as the source of URLs. Usage is only implied.

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