Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nymag_article

Fetch New York Magazine article content by canonical URL, returning title, authors, section, lead image, paywall flag, and body paragraphs.

Instructions

Get New York Magazine article content. Returns a New York Magazine article by its canonical url: title, description, section, authors, lead image, publication and update times, a paywalled flag and the body paragraphs. Subscriber-only or blocked articles return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical New York Magazine article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 meaningful work: it enumerates the returned fields, flags a `paywalled` marker, and discloses that subscriber-only or blocked articles yield an upstream error. It lacks auth/rate-limit notes, but the error and paywall disclosure is genuinely useful context.

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?

Front-loaded with purpose, then the return fields, then the error condition. Efficient overall, though the returned-field enumeration is a fairly long clause. Every sentence earns its place.

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 usefully explains the return payload and the paywall/error behavior. It covers what an agent needs to call and interpret the result, with only auth details left unstated.

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, so the schema already documents it fully. The description restates 'canonical url' but adds no syntax or format detail beyond the schema; baseline 3 is correct.

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+resource ('Get New York Magazine article content... Returns a New York Magazine article by its canonical url') and its scope is clearly the full article, distinguishing it from sibling list tools like nymag_headlines/nymag_news and from nymag_author.

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 the 'by its canonical url' framing and sibling contrast, but the description never states when to prefer this over nymag_headlines or nymag_news, nor any prerequisite beyond supplying a URL. Adequate but no explicit 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