Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbc_search

Find public BBC pages by query and return a bounded page of result metadata, including title, URL, summary, date, and content type.

Instructions

Search public BBC pages. Returns a bounded page of public BBC search-result metadata: title, URL, standfirst summary, display date, and a type of article, video, audio, live, topic, or page. Topic items are BBC topic hub pages rather than articles and carry no published_at. Media entries link only to their BBC landing pages; streams, downloads, and transcripts are not returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query, up to 120 characters
pageNoResults page, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a basic statement by explaining that results are a bounded page, that topic items are hub pages without published_at, and that media entries only link to landing pages with no streams/downloads/transcripts. This is substantive transparency about what the tool actually returns.

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?

The description is four sentences long, front-loaded with the core purpose, and every sentence adds value: scope, return fields, item type caveats, and exclusions. There is no redundancy or padding.

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?

Given the absence of an output schema certainty and annotations, the description effectively explains what the tool returns: field names, item types, and key distinctions. It is complete for a simple search tool, though it does not cover pagination behavior beyond the page parameter, which is already self-explanatory in the schema.

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 description coverage is 100% for both parameters (q and page). The description adds a high-level 'bounded page' context but does not enrich parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource ('Search public BBC pages') and then details the exact return metadata (title, URL, standfirst summary, display date, type). This clearly distinguishes it from sibling tools like bbc_article or bbc_headlines, which fetch specific content rather than performing a search.

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 description implies usage context (searching public BBC content) and lists what is not returned (streams, downloads, transcripts), but it never explicitly says when to prefer this tool over alternatives or names sibling tools. The guidance is implied rather than stated.

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