Fetch breaking news and headlines from Associated Press (AP News), a leading global news agency. Returns article title, summary, canonical URL, publication timestamp, and journalist byline. Use for current events coverage, news monitoring, or building newsfeeds. Best for recent breaking stories published within 24 hours.
| Name | Required | Description | Default |
|---|---|---|---|
| max_results | No | Number of recent articles to fetch (default 10, max 100 for pagination) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds value by detailing the return fields (title, summary, URL, timestamp, byline) and the 24-hour recency scope. No contradictions.
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?
The description is two sentences with no extraneous information. It front-loads the core purpose and follows with usage guidance. Every sentence earns 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?
Given the single parameter, high schema coverage, and clear annotations, the description is complete. It covers the tool's output, intended use, and recency constraint, requiring no further elaboration.
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 only parameter, max_results, is fully described in the schema (coverage 100%). The tool description does not provide additional context about the parameter beyond what the schema offers, so a baseline score of 3 is appropriate.
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 clearly states 'Fetch breaking news and headlines from Associated Press (AP News)', specifying the verb 'Fetch' and the resource 'AP News'. It also lists the returned fields, differentiating it from sibling tools like get_bbc_news by naming the source.
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 includes 'Use for current events coverage, news monitoring, or building newsfeeds. Best for recent breaking stories published within 24 hours', providing clear usage context. While it does not explicitly contrast with siblings, the source-specific guidance is sufficient for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool retrieves news from a distinct source (AP, BBC, HN, NPR, Google News) with no functional overlap, making it easy for an agent to select the correct one.
All tool names follow the consistent 'get_<source>_news' pattern in snake_case, providing a clear and predictable naming convention.
With 5 tools covering major global and niche news sources, the count is well-scoped for the server's purpose without being overwhelming or insufficient.
The set covers a broad range of news sources (global, US, UK, tech), though missing some major outlets like Reuters or an ability to fetch by category, but core retrieval is solid.