Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nypost_headlines

Retrieve recent New York Post headlines for a specified section slug, returning story titles, URLs, summaries, authors, and publication times.

Instructions

Get New York Post section headlines. Returns recent New York Post stories for one section. section is required and takes one of 54 slugs, such as us-news, metro, nfl, business, real-estate or astrology. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesNew York Post RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the return shape ('title and URL, and may include summary, author, publication time and image'), which is genuinely useful. However, it says nothing about pagination, result limits, or whether the list is a live feed versus a snapshot, leaving meaningful behavioral gaps.

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?

Three tight sentences with the core purpose front-loaded, followed by the constraint and the return shape. Every sentence earns its place; no filler or redundancy beyond a minor restatement of the required-section constraint.

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?

There is no output schema, so the description usefully covers the return fields, and the single required parameter is fully documented in the schema. It is nearly complete for a simple headlines tool, though pagination/result-count behavior is unaddressed.

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 enum already enumerates all 54 slugs, so the schema does the heavy lifting. The description restates 'one of 54 slugs' and gives example values, which adds marginal confirmation but no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 Post section headlines' and clarifies it returns 'recent New York Post stories for one section.' The scope (a single section) is clear, but no sibling tool (nypost_news, nypost_sections, nypost_article) is named to disambiguate, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never states when to use this tool versus alternatives like nypost_news or nypost_sections, nor does it give any exclusions or prerequisites. Usage is only inferable from the purpose statement, with no 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