Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailyexpress_headlines

Retrieve headlines for a specified Daily Express section by slug, returning each article's title, URL, summary, publication time, and image.

Instructions

Get Daily Express section headlines. Returns the latest Daily Express headlines for one section. section is required and takes a slug such as news, royal, showbiz-tv, formula-1 or city-business. Each item has its title, URL, summary, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesDaily Express section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/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 disclosure burden. It usefully describes the return shape (title, URL, summary, publication time, image), which is valuable since no output schema exists, but it omits pagination, rate limits, and any auth considerations.

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 sentences, zero waste, front-loaded with the core action and resource. The required-parameter constraint and the return-field list follow logically without 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?

For a single-parameter, no-output-schema tool, the description covers the action, the required parameter, example values, and the returned fields. It is nearly complete, with only the absence of usage routing against sibling news tools as a minor gap.

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 enum fully enumerates valid slugs, so the schema does the heavy lifting. The description adds example slugs ('news', 'royal', 'showbiz-tv', 'formula-1', 'city-business') that illustrate but largely duplicate enum values, making it a baseline 3.

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 ('Get') and resource ('Daily Express section headlines') and clarifies it returns headlines for a single, required section. An agent can distinguish it from article/news tools, though it never explicitly names how it differs from dailyexpress_news or dailyexpress_sections.

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 `section` slug and the 'one section' framing, but there is no explicit when-to-use versus alternatives (e.g. when to prefer headlines over article or news) and no exclusions or prerequisites 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