Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

standard_headlines

Fetch Evening Standard headlines for a specific section using a slug like news/london. Returns title, URL, summary, publication time, author, and image.

Instructions

Get Evening Standard section headlines. Returns the latest Evening Standard headlines for one section. section is required and takes a slug such as news/london, news/politics, sport/football, business/markets, culture/theatre or homesandproperty/renting. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesEvening Standard RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 usefully discloses the return shape (title, URL, summary, publication time, author, image) and that results are the 'latest' headlines, but says nothing about item count, ordering, pagination, or caching behavior for a live feed.

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?

Three short sentences, front-loaded with the purpose before parameter and return details. The first two sentences are mildly redundant (both restate fetching headlines), which is the only waste.

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 one-parameter read tool with no output schema, the description covers purpose, the required parameter, and the fields returned, which is what an agent needs to call it. Minor gaps in ordering/count remain but are not critical for correct invocation.

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% and the single `section` parameter is a fully enumerated slug list, so the schema already documents all valid values. The example slugs in the description ('news/london', 'sport/football', etc.) restate values already present in the enum, adding no new semantics beyond the baseline.

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 and resource ('Get Evening Standard section headlines') and scopes it to a single section, which implicitly distinguishes it from a broad news feed. It does not name sibling tools like standard_news or standard_sections, so an agent must infer the boundary, keeping it 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?

The description conveys that the tool is for one specific section and that `section` is required, which implies when to reach for it. However, it offers no explicit when-to-use vs alternatives (e.g. standard_news for the general feed) and no exclusions or prerequisites, leaving usage 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