Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nyt_article

Extract a New York Times article's title, metadata, authors, keywords and body paragraphs from its canonical URL for structured reading or analysis.

Instructions

Get a New York Times article's content. Returns a New York Times article by canonical url, with title, description, published_at, updated_at, section, authors, keywords, image_url and the body paragraphs in order. Query strings and fragments are stripped. A subscription barrier returns 403, and non-article or non-NYT URLs return 400.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical NYT 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?

With no annotations, the description carries the full behavioral burden and does so richly: it discloses URL normalization (query strings and fragments stripped), HTTP 403 for the subscription barrier, and 400 for non-article or non-NYT URLs. These are exactly the failure modes an agent needs before invoking.

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?

Front-loaded with the purpose, followed by the return shape, then normalization rules, then error semantics. Every sentence is load-bearing and there is no filler, so the length is justified.

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?

There is no output schema, so the description must explain returns -- and it enumerates all returned fields (title, description, timestamps, section, authors, keywords, image_url, ordered paragraphs). Combined with the error and URL-normalization coverage, an agent has everything needed for a correct call.

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 already 100% for the single `url` param, so the baseline is 3. The description adds value beyond the schema by defining what 'canonical' means (query strings/fragments are stripped) and warning that non-NYT or non-article URLs return 400, which clarifies the accepted input domain.

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?

Opens with a specific verb+resource ('Get a New York Times article's content') and immediately scopes it to fetching a single article by canonical URL. This cleanly distinguishes it from NYT siblings like nyt_headlines, nyt_sections, and nyt_author, which enumerate rather than retrieve a single article.

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 by 'by canonical `url`', making it clear this tool is for retrieving a known article. However, it never says when to prefer it over siblings (e.g., 'use nyt_headlines to discover URLs first') nor states preconditions beyond the URL shape. Adequate but no explicit routing guidance.

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