Retrieve Breitbart's current editorial sections, providing verified category inventory for use with the headlines endpoint.
Get Breitbart sections. Returns the live-verified public Breitbart editorial section inventory used by the headlines endpoint.
| 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 present, so the description carries the full burden. It adds useful behavioral context such as 'live-verified' and 'public,' but it does not describe output shape, pagination, or any other request behavior beyond returning the inventory.
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 with the core function front-loaded and no wasted words. The second sentence adds relevant provenance and downstream-usage context, earning its place.
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 zero-parameter, read-only lookup, this description is nearly complete: an agent knows what it returns and why it exists. A note on the exact return shape would be slightly helpful given the absence of an output schema, but the low complexity keeps this adequate.
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 has zero parameters and an empty schema, so there are no parameter semantics for the description to clarify; the baseline 4 applies. No parameter explanation is needed in this case.
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 states a specific action ('Get') and resource ('Breitbart sections') and clarifies that it returns an 'editorial section inventory.' It does not explicitly name a sibling alternative, but the reference to the headlines endpoint helps distinguish it from headline/news 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?
The phrase 'used by the headlines endpoint' gives clear context for when this tool is relevant: when an agent needs the section inventory that headlines are organized by. It does not explicitly state when not to use it or mention alternatives, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.