Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

rte_author

Fetch an RTÉ News author profile by canonical URL to retrieve name, headshot, role, and recent articles with titles, links, summaries, times, and images.

Instructions

Get an RTÉ News author profile. Returns an RTÉ News author's profile by canonical url (https://www.rte.ie/author/<id>-<slug>/, the author link on an article byline): name, headshot, role and recent articles, each with title, URL, summary, publication time and image. role is the job title the page shows, for example Political Correspondent, and is omitted when there is none.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical RTÉ author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 helpfully discloses a data-quality behavior ('role is omitted when there is none') and implies a read-only retrieval, but says nothing about pagination/limits on 'recent articles', auth requirements, or failure behavior for non-canonical URLs.

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?

Front-loaded with the purpose, then the input format, then the return shape. Dense but every clause carries information; the packed second sentence is slightly heavy but not padded.

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, the description correctly takes on the job of describing returns (name, headshot, role, recent articles with title, URL, summary, publication time, image). The one gap is how many 'recent articles' are returned and whether the list is paginated.

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% but the schema description is only 'Canonical RTÉ author URL'. The description goes beyond it by giving the exact URL shape (`https://www.rte.ie/author/<id>-<slug>/`) and telling the agent where to obtain such a URL — real added meaning over the structured field.

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 an RTÉ News author profile') and immediately enumerates what a profile contains (name, headshot, role, recent articles). The mention that the `url` is 'the author link on an article byline' cleanly separates it from siblings like rte_article, rte_headlines and rte_sections without needing the schema.

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?

Usage is implied rather than stated: the agent learns the input comes from an article byline and that the tool is for profiles, but there is no explicit 'use this when / not when' and no named alternative for fetching article lists or headlines. Adequate context, but the agent must infer the routing.

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