Get New York Post headlines from a chosen RSS section by passing its slug. Returns clean JSON with fresh stories across news, sports, business, entertainment, and lifestyle.
Get New York Post section headlines. Returns fresh headlines from one public New York Post RSS section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | New York Post RSS section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It adds useful context: 'fresh', 'public', and 'RSS' indicate recency, no-auth access, and source format. It does not mention output shape, pagination, or error behavior, so transparency is adequate but not rich.
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?
Two short sentences, no filler, and the core action is front-loaded. Every clause adds useful information: source, freshness, and scope.
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 simple one-parameter tool with an exhaustive enum, the description is nearly complete: it states the resource, the source, and that it returns fresh headlines. Without an output schema, a bit more detail on the returned structure would be ideal, but the tool is simple enough that this is not a major gap.
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?
Schema description coverage is 100% and the section parameter already has an enum and description. The description's 'one public New York Post RSS section' reinforces this but adds little new semantic information beyond the schema.
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?
The description uses a specific verb-resource pair ('Get New York Post section headlines') and adds a precise scope qualifier ('from one public New York Post RSS section'). This clearly separates it from sibling tools that fetch articles, authors, or section lists.
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?
The description implies usage: use this tool when you need section-specific NY Post headlines. However, it does not explicitly state when not to use it or point to alternatives like nypost_news, nypost_sections, or other headline tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.