Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gbnews_headlines

Retrieve GB News headlines for a chosen section or topic path, returning each article's title, URL, summary, publication time, author, and image.

Instructions

Get GB News section headlines. Returns the latest GB News headlines for one section or topic. section is required and takes a site path such as news, news/uk/london, news/world/ukraine, news/us or news/migrant-crisis; the accepted values are listed by gbnews-sections. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesGB News section or topic path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 behavioral burden. It helpfully enumerates the returned fields (title, URL, summary, publication time, author, image) and implies recency via 'latest', but says nothing about result count, pagination, or authentication needs.

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 tight sentences, front-loaded with the purpose, then return content, then parameter guidance. Every sentence carries distinct information useful to an agent.

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 appropriately describes the item fields, and the single required parameter is fully covered. Minor gaps remain around volume of results and pagination, but for a simple read-only headlines fetch it is largely complete.

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%, setting a baseline of 3, but the description goes beyond the raw enum by explaining that `section` is a hierarchical site path and giving concrete examples ('news/uk/london', 'news/world/ukraine'). This clarifies the format and shape of the value rather than merely restating the enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get GB News section headlines') and adds scope ('for one section or topic'). It implicitly distinguishes itself from gbnews_article and gbnews_news, though it never explicitly contrasts with them, keeping it just short of a 5.

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?

Provides a useful prerequisite by pointing to `gbnews-sections` for accepted values, which tells the agent how to source the parameter. It offers no explicit when-to-use vs gbnews_news/gbnews_article guidance and no exclusions, 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