Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

dailymaverick_article

Extract public article metadata and body paragraphs from Daily Maverick URLs; flags paywalled pages when the publisher exposes an access-control marker.

Instructions

Get a Daily Maverick article. Extracts the public article metadata and body paragraphs Daily Maverick serves to an anonymous visitor. The paywalled flag is set only when the page exposes the publisher's access-control marker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Daily Maverick article or opinionista URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/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 well: it discloses that only publicly served content is extracted and precisely defines the paywalled flag as being set 'only when the page exposes the publisher's access-control marker.' It does not cover failure behavior for invalid or non-article URLs, so it is strong but not exhaustive.

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 tight sentences, purpose front-loaded, and each subsequent sentence adds real information (extraction scope, paywall semantics) rather than restating the name or schema.

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 or annotations, the description does the necessary work of saying what is returned and how the paywalled flag is determined. For a single-URL fetch tool this is nearly complete; only failure modes and any rate/access caveats are absent.

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?

There is a single 'url' parameter with 100% schema description coverage ('Canonical Daily Maverick article or opinionista URL'), so the schema already does the work. The description adds no URL format, canonicalization, or error-handling detail, which is the baseline 3 for full-coverage single-param tools.

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?

The description names a specific verb and resource ('Get a Daily Maverick article') and clarifies scope by stating it extracts public metadata and body paragraphs, which separates it from the dailymaverick_headlines/news/sections siblings that list rather than fetch. It stops short of explicitly naming an alternative, so it is clear but not fully sibling-differentiating.

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 context is implied through the anonymous-visitor framing, which tells the agent this works without credentials, but there is no explicit when-to-use guidance, no mention of the headlines/news siblings, and no statement of what input URL forms are acceptable beyond the schema's own hint.

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