Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newscomau_article

Retrieve News.com.au article content from a canonical URL, returning title, authors, publication times, paywall status, and body paragraphs as structured JSON.

Instructions

Get News.com.au article content. Returns a News.com.au article by canonical url, which must be a www.news.com.au link ending in /news-story/<32-character-id>. The response has title, description, section, authors, lead image, publication and update times, a paywalled flag and body paragraphs. authors is empty for wire or agency pieces with no byline.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical News.com.au article URL

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 full burden and does disclose meaningful behavior: the returned fields, the `paywalled` flag, and the edge case that `authors` is empty for wire/agency pieces. It omits auth requirements, rate limits, and error behavior, which keeps it from a 5.

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 sentences, zero filler: purpose first, then the URL constraint, then the response shape, then the byline edge case. Well front-loaded and 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?

With no output schema, the description steps in to describe the return fields, and it documents the single required parameter and an edge case, so an agent has what it needs to call correctly. It stops short of covering failure modes or empty-response handling.

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% so the baseline is 3, but the description goes beyond the schema's terse 'Canonical News.com.au article URL' by specifying the required domain and the /news-story/<32-character-id> path pattern. That adds real validation value an agent cannot get from the schema alone.

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 ('News.com.au article content'), and the URL-shape requirement makes it obvious this fetches a single article rather than a list. It never names the sibling list/headline tools (newscomau_news, newscomau_headlines, newscomau_sections) to make the routing explicit, so it falls short of a 5.

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 supplies a concrete prerequisite: the url must be a www.news.com.au link ending in /news-story/<32-character-id>. That tells an agent when this tool is applicable, but there is no explicit when-not or pointer to an alternative tool for discovering article URLs.

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