Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nzherald_headlines

Fetch recent NZ Herald headlines for one section, such as nz, business, politics, or world, and return each article's title and URL for news monitoring.

Instructions

Get NZ Herald section headlines. Returns recent NZ Herald headlines for one section. section is required and takes a slug listed by nzherald-sections, such as nz, business, rugby, politics or world. Each item has a title and URL. A URL may point at a premium article, which nzherald-article rejects with a permission error.

Input Schema

NameRequiredDescriptionDefault
sectionYesNZ Herald section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/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 return shape (title and URL per item), one-section scope, and the premium-article permission failure downstream. Pagination or result-count limits are not mentioned, which is the only notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the purpose, then input guidance, then output shape, then the caveat. No filler and each sentence 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?

For a one-parameter headlines tool with no output schema, the description covers inputs, return item shape, and a downstream failure mode. Missing only secondary details like result ordering or count, which are minor for this tool class.

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 enumerates all 44 slugs, so the baseline is 3. The description adds real value by stating the parameter is required and, more importantly, that valid values come from `nzherald-sections` — telling the agent how to discover values rather than guessing.

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 and resource ('Get NZ Herald section headlines') and names scope ('one section'). It is distinguishable from nzherald_sections (slug enumeration) and nzherald_article (full article fetch) without opening any 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?

Explicitly routes the agent to `nzherald-sections` for valid slugs and warns that premium URLs returned here will fail in `nzherald-article`. It does not explicitly contrast with siblings like nzherald_news, but the context is clear.

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