Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

men_headlines

Fetch current Manchester Evening News headlines for a chosen section, returning titles, URLs, summaries, publication times and images.

Instructions

Get Manchester Evening News section headlines. Returns current Manchester Evening News headlines for one section. section is required and takes a slug such as news, news/greater-manchester-news, sport/football/transfer-news, whats-on/theatre-news or trips-and-breaks. Each item has its title, URL, summary, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesManchester Evening News 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?

With no annotations, the description carries the full behavioral burden. It usefully discloses the shape of each returned item (title, URL, summary, publication time, image), which is valuable since there is no output schema. But it omits count/limit, pagination, freshness, and any error behavior for invalid slugs, so substantial behavioral context is missing.

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 the core purpose and kept to a few efficient sentences. It is slightly redundant in repeating 'Manchester Evening News headlines' and re-declaring the required parameter, but overall there is little wasted prose.

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 read tool with no output schema, the description covers the essential contract: what it fetches, the required slug, and the fields returned per item. It stops short of pagination or result-count details, but the definition is complete enough 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 description coverage is 100% and the enum already enumerates all valid slugs. The description restates that `section` is required and provides example slugs that overlap with the enum values, adding readability but little semantic information beyond the schema.

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 Manchester Evening News section headlines') and scopes it to one section, so it is distinguishable from a general news feed. However, it does not name or contrast with close siblings such as men_sections (which would list sections) or men_news, leaving that routing to inference.

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 by 'one section' and the required `section` slug, which suggests this tool fetches one section's headlines rather than everything. No explicit when-to-use/when-not-to-use guidance or named alternatives are given, so an agent must infer the boundary with men_sections and men_news.

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