List Page Six RSS section slugs with display names and URLs to find valid sections for headlines requests, including celebrity, royal family, and Taylor Swift feeds.
Get Page Six RSS sections. Lists the 30 Page Six section slugs accepted by pagesix-headlines, such as celebrity-news, royal-family, taylor-swift and palm-beach-society. Each entry has its slug, display name and url.
| 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?
With no annotations, the description carries the disclosure burden and does well: it reveals the cardinality (30 sections) and the exact shape of each returned entry (slug, name, url), which is meaningful for a read-only discovery tool. It does not mention auth or rate limits, but none are implied for an RSS listing.
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 tight sentences: what it returns, how it relates to the consumer tool with concrete slug examples, and the entry shape. Nothing is redundant and the key relationship is front-loaded.
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 no-param, no-output-schema listing tool, the description supplies exactly what is missing elsewhere: the return structure and the linkage to pagesix-headlines. An agent has everything needed to call and use it.
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, so the schema has nothing to document and the baseline of 4 applies. The description does not need to compensate for missing parameter info.
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 names a specific verb (Get) and resource (Page Six RSS sections) and explicitly frames the output as the section slugs accepted by pagesix-headlines. This cleanly distinguishes it from the sibling pagesix_headlines/news/article tools.
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?
By stating the slugs are 'accepted by `pagesix-headlines`', it strongly implies this is the discovery step to run before querying headlines. There is no explicit when-not or alternative callout, but the intended workflow context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.