Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nypost_article

Fetch New York Post article content from its canonical URL. Returns title, authors, section, publication/update times, paywall status, and body paragraphs as structured JSON.

Instructions

Get New York Post article content. Returns a New York Post article by canonical url in the form https://nypost.com/YYYY/MM/DD/<section>/<slug>/: title, description, section, authors, lead image, publication and update times, a paywalled flag and the body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical New York Post 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 behavioral burden and does disclose the return shape in detail (title, description, section, authors, lead image, times, paywalled flag, paragraphs), notably the paywalled flag. It omits auth/rate-limit behavior, but for a read-only fetch the disclosed content is genuinely useful.

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?

Two sentences, purpose front-loaded, then a compact enumeration of returned fields. No wasted words; the field list doubles as output documentation.

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?

No output schema exists, so the description's field enumeration substitutes for it, and the single required parameter is well specified. Missing only usage routing among sibling tools, which is minor for a simple by-URL fetch.

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% (baseline 3), and the description adds meaningful value by specifying the exact canonical URL pattern `https://nypost.com/YYYY/MM/DD/<section>/<slug>/`, which is more precise than the schema's generic 'Canonical New York Post article URL'.

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') and resource ('New York Post article content') and distinguishes itself from the sibling nypost_headlines/nypost_news/nypost_sections tools by being the single-article fetch. An agent can tell immediately this retrieves one article by URL.

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 is implied: it fetches an article given a canonical URL, and the URL format constraint hints at the required input. However, it never states when to use this versus nypost_headlines or nypost_news, nor any prerequisites or exclusions.

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