Get current New York Post top stories and headlines immediately. Retrieve titles, URLs, and summaries of the most recent news from the publication.
Get New York Post top stories. Returns the current New York Post top stories, with no parameters. Each item has a title and URL, and may include summary, author, publication time and image. Use nypost-headlines to read a single section.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden, and it does disclose the return shape: a title and URL per item, optionally summary, author, publication time and image. That is genuinely useful given no output schema exists, though freshness/caching or rate-limit behavior is not addressed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences: purpose first, then return shape, then the sibling routing hint. Every sentence earns its place and nothing is padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, read-only news feed with no annotations and no output schema, the description covers purpose, return fields and an alternative tool. Return-field coverage is good; only freshness/ordering semantics are left unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, which is the baseline-4 case. The description reinforces this by stating 'with no parameters', leaving no ambiguity that no filtering or identifier is accepted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 top stories') and explicitly differentiates from the sibling nypost-headlines by scoping this to overall top stories vs a single section. An agent can distinguish it from nypost_article, nypost_author and nypost_headlines without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent to nypost-headlines for the 'read a single section' case, giving a clear alternative with its selection condition. It does not mention the other siblings (nypost_article, nypost_sections), so the when-to-use guidance is clear but not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.