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, so safety is covered. The description adds valuable behavioral details: it enumerates the return fields (title, summary, URL, timestamp, byline) and states the 24-hour recency limit, which helps set expectations beyond the annotations.
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 concise sentences serve distinct purposes: purpose, output fields, and usage guidance. There is no redundant wording, and the most important information 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 simple tool with one optional parameter and no output schema, the description covers all necessary context: what it does, what it returns, when to use it, and its recency limitation. Combined with annotations, the agent has enough information to select and invoke the tool correctly.
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 schema has 100% coverage for the single parameter max_results, including default and max values. The description doesn't mention the parameter directly, so it adds no extra semantic meaning. Baseline of 3 is appropriate when schema fully documents the parameter.
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 the action (fetch breaking news and headlines) and the resource (Associated Press/AP News), and identifies it as a leading global news agency. This distinguishes it from sibling tools like get_bbc_news or get_hacker_news by specifying the exact news 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 provides clear usage context: 'Use for current events coverage, news monitoring, or building newsfeeds' and 'Best for recent breaking stories published within 24 hours.' It doesn't explicitly mention alternatives or exclusions, but the temporal constraint and use cases give practical guidance.
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 targets a distinct news source or search functionality. The four get_* tools are differentiated by provider, and search_google_news complements them with cross-source search, eliminating ambiguity.
All tool names follow a clear verb_source pattern: get_ or search_ followed by the source identifier. This consistent convention makes the tool's function predictable from its name alone.
With five tools covering four major news providers plus a global search, the count is well-scoped for a news fetching server. Neither too sparse nor overwhelming.
The surface covers both source-specific top stories and keyword-based cross-source search, meeting the core needs of news retrieval. No critical gaps are apparent for the stated purpose.