Retrieve top Breitbart news stories without input; get titles, canonical URLs, summaries, publication times, authors, and images in clean JSON.
Get Breitbart top stories. Returns the latest Breitbart top stories from across the site, with no input needed. Each item has a title and canonical URL, and may also carry a summary, publication time, author and image.
| 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 carries the full burden, and it does disclose the return shape (title + canonical URL plus optional summary, time, author, image) which is genuinely useful given no output schema exists. It omits freshness, result count, and pagination behavior, so the behavioral picture is only partial.
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 compact sentences, front-loaded with the purpose and then the return fields; nothing is padded, and "from across the site" adds real scoping value rather than filler.
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?
With no output schema, no annotations, and zero params, the description supplies the essential pieces: what it returns and the item fields. It is nearly sufficient, missing only a note on how many stories come back and whether the list is cached or live.
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 confirms "no input needed," correctly setting the expectation that no arguments are required or 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?
Clear verb+resource ("Get Breitbart top stories") and scope ("from across the site"), so an agent knows this pulls a front-page-style listing. It does not, however, distinguish itself from the nearby sibling breitbart_headlines, leaving ambiguity about which listing endpoint to pick.
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?
"No input needed" hints that this is a zero-argument convenience call, but there is no explicit when-to-use guidance and no mention of the obvious alternatives (breitbart_headlines, breitbart_sections, breitbart_article). The agent must guess how this differs from the headlines tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.