Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sevennewsau_article

Fetch 7NEWS Australia article content from a canonical URL, returning metadata and body paragraphs. Flags paywalled content when present.

Instructions

Get 7NEWS Australia article content. Returns public 7NEWS article metadata and body paragraphs from a canonical 7news.com.au article URL. 7NEWS articles are free to read; a non-free content tier, if one ever appears, is flagged as paywalled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical 7NEWS 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. It discloses that articles are free to read and that a non-free tier, if present, is flagged as paywalled. This is relevant behavioral context beyond the schema, though it omits specifics like error handling or response shape.

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. The core action and return type are front-loaded, and the paywall note is useful and placed last. Every sentence adds value.

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 article fetcher with no output schema, the description covers the essential return contents (metadata and body paragraphs) and the only notable behavioral nuance (paywall flag). Nothing critical for calling it correctly is missing.

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?

Schema coverage is 100% and the schema already describes the URL parameter as 'Canonical 7NEWS article URL'. The description reiterates this constraint ('from a canonical 7news.com.au article URL') but adds no new semantic detail, so it meets the baseline for high coverage.

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 states a specific verb ('Get'), a clear resource ('7NEWS Australia article content') and the input type (canonical 7news.com.au URL). The outlet name distinguishes it from dozens of sibling article tools for other publishers, so the purpose is unambiguous.

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 implies usage for 7NEWS articles by naming the outlet and requiring a canonical URL. It doesn't explicitly mention alternatives or exclusions, but given the sibling set is dominated by other outlets' article tools, the intended context is clear enough.

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