Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

bbc_author

Fetch a BBC News correspondent's profile from a canonical URL, including name, bio, and recent articles with title, section, and publication date.

Instructions

Get a BBC News correspondent's profile. Returns a BBC News correspondent's profile from url, a canonical bbc.co.uk/news/correspondents/<slug> address: name, short bio and recent articles with title, URL, section and publication date when the page shows one. published_at is YYYY-MM-DD when the page gives a full date; items labelled only with a relative time, such as 2 days ago, come back as written.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical BBC News correspondent URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 load, and it discloses meaningful behavior: the expected canonical URL shape and, notably, that relative timestamps like '2 days ago' are returned verbatim while full dates become YYYY-MM-DD. It omits auth/rate-limit/error behavior, so not a 5.

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 return contents and then the date-handling nuance. Every sentence is informative, though the 'profile' phrasing is repeated across the first two sentences, which is mild 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?

There is no output schema or annotations, so the description must cover returns — and it does, enumerating fields and the date edge case. Given a single required param and this output detail, an agent has enough to call it correctly; only error/invalid-URL behavior is unspecified.

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%, so baseline is 3, but the description adds real meaning beyond the schema's terse 'Canonical BBC News correspondent URL' by spelling out the bbc.co.uk/news/correspondents/<slug> pattern. This clarifies the expected input format the schema leaves abstract.

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 ('BBC News correspondent's profile'), and the body enumerates exactly what the profile contains (name, bio, recent articles). An agent can distinguish it from sibling article/headline tools without opening 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 through the required canonical URL and the 'profile' framing, but there is no explicit when-to-use guidance and no mention of alternatives such as bbc_article, bbc_headlines, or bbc_search, nor how to obtain a valid correspondent URL. Adequate but leaves routing to inference.

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