Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

newyorker_article

Fetch The New Yorker article content from a canonical URL, returning metadata and body paragraphs. Detects metered paywall gating, indicating truncated text and free-access status.

Instructions

Get The New Yorker article content. Returns public The New Yorker article metadata and body paragraphs from a canonical article URL. The New Yorker uses a metered paywall: when a page marks itself as gated, only the publicly served text is returned and is_truncated is true; is_accessible_for_free reports the page's own access flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical The New Yorker article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It goes beyond a generic fetch by explaining the metered paywall behavior, the is_truncated flag, and the is_accessible_for_free flag, which is valuable for interpreting results. It doesn't cover all potential behaviors, but the key paywall nuance 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 sentences, all informative and free of filler. The main purpose is front-loaded, followed by return contents and then the paywall caveat. Each 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 one-parameter article retrieval tool, the description is complete: it states what is returned (metadata and body paragraphs), the source (canonical URL), and the behavior when paywalled. No output schema is present, so the description adequately covers what an agent needs to invoke and interpret the result.

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% for the single url parameter, and the schema already describes it as a 'Canonical The New Yorker article URL.' The description adds no new parameter semantics beyond that; baseline 3 is appropriate because the schema does the heavy lifting.

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 ('The New Yorker article content'), and further specifies it returns metadata and body paragraphs from a canonical article URL. This clearly distinguishes it from sibling tools like newyorker_sections, newyorker_author, or newyorker_headlines.

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 implies usage context: invoke when you have a canonical The New Yorker article URL and want its content. It does not explicitly name alternatives or give when-not-to-use guidance, but the canonical-URL condition is specific enough for an agent to select this tool correctly.

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