Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nzherald_author

Fetch structured NZ Herald author profile data from a canonical author URL, including bio, job title, location, email, image, and recent articles.

Instructions

Get an NZ Herald author profile. Returns an NZ Herald author profile from a required url in the form https://www.nzherald.co.nz/author/<slug>/. The response has name, job_title, location, email, biography, image_url and recent articles. Each field reflects what the author's page shows, and article published_at is RFC3339 where the page gives a machine-readable timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical NZ Herald author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 full burden and does reasonably well: it reveals the response shape, notes the profile data mirrors the page, and flags that article published_at is RFC3339 only when a machine-readable timestamp is present. It omits whether this is strictly read-only, error behavior for bad URLs, or whether the article list is paginated.

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 action, then the input contract, then the response contract. Very little waste, though sentence two restates the act of returning a profile already covered by sentence one.

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 compensates by enumerating the returned fields and the timestamp format. For a single-parameter read tool this is close to complete; only edge-case behavior (invalid URL, article list limits) is left unstated.

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 there is only one parameter, so the schema baseline already handles it; the description goes further by supplying the concrete URL template, which the schema's terse "Canonical NZ Herald author URL" does not.

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 an NZ Herald author profile") and immediately names the exact input shape and returned entity, distinguishing it from sibling nzherald_article/news/headlines tools. An agent can tell it retrieves a person profile rather than an article.

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?

The description makes the precondition explicit: it needs a required canonical author URL of the form /author/<slug>/. It gives clear context for when the tool applies, but names no alternative (e.g., nzherald_article for content) and doesn't say what to do without an author URL in hand.

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