Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nydailynews_article

Retrieves New York Daily News article content from a canonical URL, returning metadata and body paragraphs. For paywalled articles, provides the free lead-in and flags paywalled status.

Instructions

Get New York Daily News article content. Returns public New York Daily News article metadata and body paragraphs from a canonical article URL. For subscriber-only articles the response carries the free lead-in with paywalled set to true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical New York Daily News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description covers the behavioral trait of paywalled content, stating that subscriber-only articles will have free lead-in and paywalled set to true. This is important and not reflected in structured data.

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, clearly front-loaded with the main action and resource. No wasted words, informative and efficient.

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?

Given a simple tool with one parameter and no output schema, the description is sufficient. It explains the purpose, the required input, and a key behavioral aspect (paywalled). Missing details like return format are minor due to lack of output schema.

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% and the url parameter already has a description. The description reinforces 'canonical' URL but doesn't add extra semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets New York Daily News article content from a canonical URL, including metadata and body paragraphs. It distinguishes from siblings by explicitly naming the publication, though it doesn't differentiate among other article-retrieval tools.

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?

The description implies use when you have a canonical article URL, but doesn't provide explicit when-not conditions or alternatives. It doesn't mention when to use this over other article tools.

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