Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

axios_article

Retrieve Axios article metadata and full body paragraphs from a canonical URL. Subscriber-only stories return a clear 403 error instead of empty content.

Instructions

Get Axios article content. Returns a public Axios article's metadata and full body paragraphs from a canonical article URL. Subscriber-only stories with no free preview return a 403 permission error instead of an empty body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical www.axios.com 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 well: it specifies the return payload (metadata and body paragraphs) and explicitly calls out that subscriber-only stories without a free preview yield a 403 error instead of an empty body. It does not cover other edge cases like invalid URLs or rate limits, but the key failure mode is disclosed.

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 short sentences with no filler. The main verb and resource are first, followed by return details, then the critical 403 edge case. Everything 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 one-parameter tool with no output schema, the description covers what it returns and the most important error behaviour. It doesn't spell out the exact metadata fields, but 'metadata and full body paragraphs' is reasonably complete for an agent to invoke it correctly.

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 as 'Canonical www.axios.com article URL.' The description reaffirms 'canonical' and 'public,' which is mildly redundant but reinforces the expected input; no substantial extra semantics are added beyond the schema.

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 ('Get'), resource ('Axios article content'), and output ('metadata and full body paragraphs'). The phrase 'from a canonical article URL' and the source name Axios distinguish it from axios_headlines/axios_categories and other publishers' article tools.

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 clearly indicates the tool is for retrieving full content of a single Axios article given its canonical URL. It does not explicitly name alternatives (e.g., axios_headlines for lists) or state when not to use it, 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