Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theage_headlines

Retrieve current headlines for any The Age section, including titles, URLs, summaries, authors, and publication times. Specify the section slug to get structured JSON data.

Instructions

Get The Age section headlines. Returns the current stories for one The Age section: title, canonical URL, summary, author, publication time, and image where the section lists them. section must be one of the slugs returned by /theage/sections; any other value is rejected with a 400 before The Age is contacted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection slug from /theage/sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 full behavioral burden. It discloses the exact returned fields (title, canonical URL, summary, author, publication time, image where listed) and the pre-call validation behavior. Pagination and rate limits are not mentioned, but for a simple read tool this is solid.

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?

Three sentences with no filler: purpose, return fields, and validation constraint each get one front-loaded sentence. Every sentence earns its place.

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 single-parameter read tool with no output schema, the description tells the agent what to pass, where to get valid values, the failure mode, and what fields to expect in the response. It does not specify pagination or empty-section behavior, but those are minor gaps at this complexity.

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?

The schema already covers 100% of the parameter with an enum of valid slugs and a description referencing /theage/sections. The description mostly restates the validity requirement and adds the 400-rejection behavior, which is useful but not new parameter meaning. The 'one section' clarification is marginal.

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 The Age section headlines,' and further narrows to 'one The Age section,' which separates it from tools like theage_sections or theage_article. The listed return fields also make the tool's purpose concrete.

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?

Clear use context: call when you need current stories for a single section. It explicitly tells the agent that section must be a slug from /theage/sections and that invalid values are rejected with a 400 before The Age is contacted. It does not name a when-not alternative, so it stops short of a 5.

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