Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbc_headlines

Fetch BBC News section headlines, defaulting to world, and return titles, URLs, summaries, and publication times for selected sections.

Instructions

Get BBC News section headlines. Returns fresh BBC News headlines for one section, world by default. section can be all, world, uk, politics, business, health, science_and_environment, technology or entertainment_and_arts; all can mix stories from several sections. Each item has a title, URL, summary and publication time when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoBBC News RSS section, defaults to world

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / section / enum
      Added value: +[
+  "all",
+  "world",
+  "uk",
+  "politics",
+  "business",
+  "health",
+  "science_and_environment",
+  "technology",
+  "entertainment_and_arts"
+]
  2. Addedv1.16.2

TDQS

A3.9/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 it does disclose the return shape (title, URL, summary, publication time when available) plus the default and the mixing behavior of `all`. It omits pagination, rate limits, and freshness guarantees, but for a read-only news feed the disclosure is solid.

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 purpose, then details, and no wasted framing sentences. The one inefficiency is repeating the full enum list that the schema already carries.

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?

For a single optional-enum tool with no output schema, the description covers the default, the enum behavior, and the returned item fields, which is enough to call it correctly. Only the absence of any freshness/recency or pagination note keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the `section` enum and its default, making 3 the baseline. The description re-lists the enum values (redundant) but does add one genuine semantic detail: that `all` can mix stories from several sections.

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?

The description gives a specific verb and resource ('Get BBC News section headlines') and scopes it clearly to one section with a stated default. An agent can distinguish it from bbc_article, bbc_live and bbc_search because it explicitly returns headline lists per section.

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?

It states the default section (`world`) and explains that `all` mixes stories from several sections, which implies when each is appropriate. However, it never says when to prefer this over siblings like bbc_article or bbc_search, so 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