Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

news24_headlines

Fetch headlines for a specified News24 section path, such as business/markets or politics, returning titles, URLs, and subscriber-only flags.

Instructions

Get News24 section headlines. Returns News24 headlines for one section. section is required and takes a path such as business/markets, sport/rugby/springboks or politics, from the 73 listed by news24-sections. Each item has a title and URL, and type is subscriber on cards News24 marks subscriber-only. Summary, author, publication time and image appear when available.

Input Schema

NameRequiredDescriptionDefault
sectionYesNews24 section path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and does useful work: it discloses the result shape (title + URL per item), flags that `type` is `subscriber` on paywalled cards, and notes summary/author/time/image are conditional. It doesn't cover auth, rate limits, or result count, but the output semantics are unusually well specified.

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 purpose, then required-parameter format, then return shape — logical order with no filler. Four sentences is slightly more than strictly needed, but each carries distinct information.

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?

No output schema exists, so the description appropriately explains the return fields and the meaning of `type: subscriber`, which the agent would otherwise not know. Combined with the fully-covered enum parameter and the cross-reference to news24-sections, it is complete enough to call correctly.

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 already enumerates all 73 valid paths, so the schema does the heavy lifting. The description reinforces format with example paths and cross-references news24-sections, but the examples duplicate enum values already present, so added meaning is marginal. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get News24 section headlines') and immediately scopes it ('for one section'), which cleanly separates it from siblings like news24_sections (lists sections) and news24_news. An agent can identify the tool's job without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context ('one section') and routes the agent to the sibling `news24-sections` as the source for valid paths, which is real when-to-use guidance. It stops short of explicitly distinguishing this from news24_news or news24_article, so no full exclusion logic.

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