Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nydailynews_headlines

Fetch New York Daily News section headlines by required slug, returning up to 100 stories with titles, URLs, timestamps, bylines, excerpts, and lead images.

Instructions

Get New York Daily News section headlines. Returns New York Daily News headlines for one section, newest first, up to about 100 stories. section is required and takes one of 36 slugs such as crime-public-safety, new-york-yankees or opinion; other values return an invalid-params error. Items carry a title and URL, plus publication time, byline, excerpt and lead image where shown. Team pages can list fewer stories out of season.

Input Schema

NameRequiredDescriptionDefault
sectionYesNew York Daily News section slug

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 carries the full behavioral burden and does so well: newest-first ordering, a ~100-story cap, invalid-params behavior for bad slugs, per-item fields, and the out-of-season caveat for team pages. It omits pagination behavior and rate limits, but the core operating characteristics are disclosed.

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 the purpose, then the return shape, then the required-parameter constraint, then item fields. Every sentence contributes; the only minor cost is that the item-field enumeration is dense and could be trimmed.

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 correctly explains what items carry (title, URL, publication time, byline, excerpt, lead image). Combined with ordering, volume cap and the team-page caveat, an agent has enough to call and interpret the tool, though pagination/limits remain unaddressed.

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% and the enum lists all 36 slugs, so the baseline is 3. The description adds real value on top: concrete slug examples and, more importantly, the failure mode that non-enum values return an invalid-params error, which the schema does not state.

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?

States a specific verb and resource ('Get New York Daily News section headlines') and the scope (one section). It is clear what the tool returns, but it never distinguishes itself from close siblings like nydailynews_news, nydailynews_sections or nydailynews_article, so the agent must infer the boundary.

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 usage (fetch headlines for one section) and warns that invalid slug values error out, which is useful. However, it gives no explicit when-to-use or when-not-to-use guidance and never routes the agent to a sibling such as nydailynews_news or nydailynews_article.

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