Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailymail_headlines

Retrieve Daily Mail headlines for a specified section, returning each item's title, URL, summary, publication time, and image so you can track news coverage by category.

Instructions

Get Daily Mail section headlines. Returns the latest Daily Mail headlines for one section. section is required and must be one of home, news, sport, tvshowbiz, health, femail, travel, sciencetech, money, debate, us or australia. Each item has its title, URL, summary, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesDaily Mail 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 discloses the return fields (title, URL, summary, publication time, image) and the 'latest' freshness semantics, but says nothing about read-only nature, rate limits, or auth requirements.

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, front-loaded sentences with no filler. The final sentence efficiently summarizes the returned fields, though repeating the full enum list is somewhat redundant with the schema.

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 headlines tool with no annotations and no output schema, the description covers purpose, the required enum, and the shape of returned items. It is nearly complete, missing only behavioral details like freshness window or read-only nature.

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 values are fully documented in the schema. The description restates the same enum list but adds no syntax or format detail beyond what the schema already provides, so baseline 3 applies.

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 opens with a specific verb+resource ("Get Daily Mail section headlines") and clarifies it returns the latest headlines for one section. An agent can tell it apart from dailymail_news and dailymail_article by the headlines-specific framing, though no sibling is named explicitly.

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?

It states that one section is required and enumerates valid sections, which implies usage. However, it gives no explicit when-to-use guidance or comparison against alternatives like dailymail_sections or dailymail_news, leaving the agent to infer the right tool.

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