Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

abcau_article

Fetch ABC News Australia article content by canonical URL: title, description, publication time, section, authors, image, and body paragraphs. Returns an error for live-blog posts.

Instructions

Get ABC News Australia article content. Returns an ABC News Australia article by url, a canonical abc.net.au address in the form /news/<date>/<slug>/<id>: title, description, publication time, section, authors, image and the body paragraphs. Rolling live-blog posts, whose slug ends -live-blog, return an error instead of partial content.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical ABC News Australia article URL

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?

With no annotations, the description carries the full burden and does a good job: it enumerates the returned fields (title, description, publication time, section, authors, image, body paragraphs) and discloses a real failure mode — live-blog posts (slug ending `-live-blog`) return an error rather than partial content. It stops short of noting rate limits, auth, or whether the URL must be pre-discovered.

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?

Two sentences, front-loaded with the core action and followed by the return shape and the single caveat. Every clause earns its place with no filler.

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?

There is no output schema, so the description must describe returns, and it lists the expected fields plus the live-blog error case, which is sufficient for correct invocation. Minor gaps (no auth/rate context, no note on URL discovery) keep it from perfect completeness.

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 'Canonical ABC News Australia article URL' by specifying the host (abc.net.au) and the exact path shape `/news/<date>/<slug>/<id>`, which materially constrains what a valid input looks like.

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?

The description opens with a specific verb+resource ('Get ABC News Australia article content') and makes clear this fetches a single article by URL, which cleanly separates it from the sibling list/aggregate tools (abcau_headlines, abcau_news, abcau_sections). An agent can identify this as the single-article fetch tool 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the required `url` parameter and the canonical URL form, and the live-blog caveat gives one exclusion. However, there is no explicit when-to-use statement and no mention of the sibling alternatives (e.g., use abcau_headlines to find URLs first), so the guidance is only implied rather than stated.

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