Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

stuff_headlines

Fetch Stuff (New Zealand) section headlines by required section slug, returning each story's title, URL, summary, time, author and image for news monitoring.

Instructions

Get Stuff section headlines. Returns the latest Stuff (New Zealand) stories for one section. section is required and takes one of 31 slugs, including slash-separated regional and sport ones such as nz-news/auckland and sport/rugby, plus world-news, business, politics and motoring. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesStuff section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/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 burden. It discloses the returned fields (title, URL, summary, publication time, author, image) and that results are 'latest', which is useful given there is no output schema. It says nothing about rate limits, pagination, or auth, but for a simple read-only headline fetch there is little additional behavior to reveal.

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 sentences, front-loaded with the purpose and scope, followed by parameter guidance and return shape. Every sentence earns its place with no padding, though it could be tightened slightly.

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?

With no output schema, the description usefully enumerates the returned fields, and the single required parameter is fully explained. For a one-parameter headline fetcher this is close to complete; only pagination/ordering details are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum already lists all 31 slugs, but the description adds real value by explaining the structure: slash-separated regional and sport slugs like nz-news/auckland and sport/rugby, plus standalone slugs. This clarifies how to interpret and pick an enum value beyond the bare list.

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 (Get) and resource (Stuff section headlines), and pins down scope: latest Stuff (New Zealand) stories for a single section. This clearly separates it from siblings like stuff_article or stuff_author, but it never explicitly names or contrasts stuff_news or stuff_sections, which an agent must infer.

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?

'Returns the latest stories for one section' implies the retrieval use case, but there is no explicit when-to-use statement and no routing to alternatives such as stuff_news or stuff_sections. The condition for choosing this tool over its siblings is left to inference.

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