Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mirror_headlines

Retrieve recent Mirror headlines for a specific section by slug; results include title, URL, and optional summary, author, publication time, and image.

Instructions

Get Mirror section headlines. Returns recent Mirror headlines for one section. section is required and takes one of 34 slugs or paths, such as news/uk-news, sport/football, 3am or lifestyle/food-drink. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesMirror 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 burden. It usefully states the return shape (each item has a title and URL, and may include summary, author, publication time and image) but does not explicitly declare the read-only, low-risk nature of the call, nor any auth, rate limit, or pagination behavior.

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?

The description is three sentences, front-loaded with purpose and then the required parameter and return shape. It is efficiently sized, though the first two sentences overlap slightly ('Get Mirror section headlines' and 'Returns recent Mirror headlines for one section').

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?

There is no output schema, and the description compensates by explaining what each returned item contains. The single required parameter is documented by the schema and reinforced in prose. The main gap is routing guidance against sibling headline tools.

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 lists all 34 section slugs. The description adds confirmation that section is required and gives representative slug examples, but this is largely redundant with the schema rather than adding new semantic detail.

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?

The description states a specific verb and resource: 'Get Mirror section headlines' and 'Returns recent Mirror headlines for one section.' That is clear and scoped. It does not explicitly distinguish itself from sibling tools such as mirror_news or mirror_sections, so it falls 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?

Usage is implied: section is required, and the slug examples show how to call it. However, there is no explicit guidance on when to use this tool versus mirror_news, mirror_sections, or other *_headlines siblings, and no when-not conditions are given.

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