Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nationalpost_article

Retrieve National Post article metadata and body paragraphs from a canonical article URL; identifies subscriber-only content and rejects category, tag, author, and Sponsored links.

Instructions

Get National Post article content. Returns public National Post article metadata and body paragraphs from a canonical article URL. paywalled is true when the publisher marks the story subscriber-only or registration-gated; National Post gates these stories in the reader's browser but still serves the complete text to an anonymous request, so paragraphs is the whole body and nothing is bypassed. Category, tag, author and Sponsored URLs are rejected with a 400.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical National Post article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond the schema to disclose the paywall behavior: paywalled is true for gated stories, but the full body is still served to anonymous requests, so nothing is bypassed. It also states non-article URLs return a 400. This is highly transparent, especially with no annotations provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise and front-loaded with the core purpose. The paywall explanation is detailed but earns its place because it resolves potential concerns about bypassing. Structurally clear, though the second sentence is somewhat long.

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, the description covers the main return aspects: metadata, body paragraphs, and the paywalled flag. It also covers error conditions. It does not enumerate all metadata fields, but for a single-parameter article fetcher, the essential context is present.

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?

The input schema already documents 'url' with 100% coverage. The description adds the key semantic that the URL must be a canonical article URL and that non-article URLs are rejected, which meaningfully clarifies the parameter 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?

The description starts with a specific verb and resource: 'Get National Post article content.' It specifies exactly what is returned (metadata and body paragraphs) and distinguishes itself from sibling tools by emphasizing canonical article URLs and rejecting Category/tag/author/Sponsored URLs.

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?

It clearly states the tool is for canonical article URLs and explicitly lists rejected URL types (Category, tag, author, Sponsored), which tells an agent when not to use it. However, it does not name sibling alternatives like nationalpost_headlines or nationalpost_news, so the when-to-use guidance is strong but not exhaustive.

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