Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailyrecord_headlines

Retrieve Daily Record section headlines by passing a required section slug such as news, sport, or money. Returns each item's title and URL, with news summaries, times, and images.

Instructions

Get Daily Record section headlines. Returns the latest Daily Record headlines for one section. section is required and must be one of news, scotland, uk-world-news, sport, football, showbiz, lifestyle, money, travel or in-your-area. Every item has its title and URL; the news section also carries summary, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesDaily Record section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/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 discloses that this is a read-style retrieval, lists the required section values, and specifies the returned fields (title and URL), including extra fields for the `news` section. It does not discuss pagination or rate limits, but for a simple fetch tool it is reasonably transparent.

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 compact and front-loads the core action. The first two sentences are slightly redundant (both state that it returns section headlines), but the enum list and return-field note are efficient and useful.

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?

Given the simple one-parameter schema and no output schema, the description provides enough to call the tool correctly: required section, allowed values, and expected return fields. Missing details such as item count or pagination are minor for a headline-list tool.

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 is fully documented in the schema. The description repeats the required parameter and its allowed values, adding little beyond the schema. Baseline 3 is appropriate when the schema already does the heavy lifting.

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 Daily Record section headlines," and clarifies it returns the latest headlines for one section. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools like dailyrecord_news or dailyrecord_article.

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 required `section` parameter and its allowed values are stated, which implies the tool is used for per-section headline retrieval. However, there is no explicit guidance on when to use this versus siblings such as dailyrecord_news or dailyrecord_article, nor any exclusions.

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