APIVerve

World News

WorldNews

Read-only

World News: World News is a global news API that reads about 275 outlet feeds in 29 editions and 6 languages and merges them into stories: one entry per story however many outlets carry it, ranked by that coverage. Filter by 13 topics, by the country a story is about, by the edition it ran in, or by language. (Cost: 6 credits)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "WorldNews"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	Only stories whose headlines or summaries contain every word given, in any case.
`list`	No	What to list: categories, editions or languages
`sort`	No	top ranks stories by how many outlets carry them, favouring the last 12 hours; latest is newest first.	top
`limit`	No	Maximum number of stories to return: up to 10 on the free plan, 50 on paid plans.
`since`	No	Only stories published at or after this date or date-time (ISO 8601), for example 2026-10-01 or 2026-10-01T14:00:00Z.
`country`	No	Only stories about this country, from any outlet: an ISO 3166 code or English name, for example JP or Japan.
`edition`	No	Only stories run by outlets based in this country: what its press is covering, in the languages it writes in. See list=editions.
`category`	No	Only stories on this topic. A story is in every topic its headline and summary name, not only its feed's section.
`language`	No	Only stories in this language. Defaults to English, or with edition to the languages that edition's press writes in. Stories are never translated.

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the description needn't restate safety. It adds real value beyond them: the deduplication behavior (one entry per story regardless of outlet count), coverage-based ranking, and an explicit cost of 6 credits per call. Pagination and rate-limit behavior are left unstated, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the aggregation model before the filter capabilities, and the credit cost is placed at the end where it is easy to scan. The opening redundantly repeats the tool name ('World News: World News is...'), which is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 optional parameters, full schema coverage, annotations and an output schema, the description supplies the missing pieces an agent needs: the dedup/ranking model and the per-call credit cost. It is slightly thin on the list= mode and on tier limits enforced by 'limit', but nothing essential for correct invocation is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains q, list, sort, limit, since, country, edition, category and language in detail. The description adds only the count of available topics (13) and the conceptual distinction between 'country a story is about' and 'edition it ran in', which is useful but largely duplicated from the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — a news reader that ingests ~275 outlet feeds across 29 editions and 6 languages and merges them into deduplicated stories ranked by coverage. That distinguishes it clearly from the financial-news sibling TickerNews and from generic feed tools without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It lists the four filter axes and the two sort modes, which implies how to use the tool (topic/country/edition/language narrowing, 'top' vs 'latest'). However, it never says when to prefer this over alternatives such as TickerNews, nor does it state exclusions or prerequisites for the paid-tier limits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APIVerve tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.