Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

scmp_article

Fetch an SCMP article's metadata and body from its canonical URL. Returns public content as served to anonymous visitors; reports restricted-access pages as errors instead of truncated responses.

Instructions

Get an SCMP article's content. Returns one public South China Morning Post article's metadata and body paragraphs from a canonical article URL. content_locked and paywall_types are the upstream's own restricted-access signals for that article, reported exactly as the site returns them; the body returned here is the same one the site's own page serves to an anonymous visitor. An article whose page genuinely withholds its body is reported as a restricted-access error instead of a hollow or truncated response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical SCMP article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries full burden. It discloses that `content_locked` and `paywall_types` are upstream restricted-access signals, that the body matches what an anonymous visitor sees, and that restricted articles are returned as an error rather than a hollow response. This clearly explains behavior without requiring inference.

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 succinct sentences, front-loaded with the primary purpose, then adding behavioral details. No waste or redundancy; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the description fully covers what it returns (metadata, body paragraphs, restricted-access signals) and how it behaves with restricted content. Nothing essential is missing for an agent to call it correctly.

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% with the 'url' parameter described as 'Canonical SCMP article URL'. The description reinforces this by saying 'from a canonical article URL', adding clarity that the URL must be canonical, which is useful beyond the schema alone.

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') and resource ('SCMP article's content'), explicitly mentioning it returns metadata and body paragraphs from a canonical URL. It distinguishes from sibling scmp_headlines/scmp_sections by focusing on single-article content retrieval.

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: when you have a canonical article URL, use this tool. It doesn't explicitly name alternatives like scmp_author or headlines, but the context is clear enough for an agent to know when to select it. It also notes it handles public articles only, which guides expectations.

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