Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

euronews_author

Fetch a Euronews author profile from its canonical URL and return name, job title, editorial team, social links, and recent articles in clean JSON.

Instructions

Get a Euronews author profile. Returns a Euronews author profile for a url like https://www.euronews.com/profiles/<id>. The response has the name, job title, editorial team, social_links (usually one X/Twitter link, empty if none) and recent articles. There is no headshot or biography, and job_title is repeated as Euronews gives it.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Euronews author profile URL

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 enumerates the returned fields, warns that `social_links` is usually a single X/Twitter link and may be empty, and explicitly rules out headshot and biography. It notes the `job_title` duplication quirk, which is genuine behavioral detail. It does not cover failure modes for malformed or non-profile URLs.

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 sentences, each doing distinct work: what it returns, what form the URL takes, and what the payload does and does not contain. Front-loaded with the purpose, no filler or restatement of the name.

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 must describe the return payload, and it does: fields listed, quirks noted, expected absences called out. The remaining gap is how many "recent articles" come back and whether they are paginated or truncated.

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 there is only one parameter, so the baseline is already a 3. The description earns above baseline by supplying a concrete URL template (`.../profiles/<id>`) that the schema's terse "Canonical Euronews author profile URL" does not illustrate.

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 a Euronews author profile") and immediately names the exact input shape (a profiles URL). The sibling list contains euronews_article, euronews_headlines and euronews_news, and the word "author" plus the profile-URL requirement cleanly separates this from article-level tools.

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 gives the decisive selection signal: the input must be a canonical profile URL of the form `https://www.euronews.com/profiles/<id>`, which tells an agent exactly which situations this tool fits. It stops short of naming alternatives (e.g. "use euronews_article for article bodies") or saying what to do when only an author name is known.

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