Tool reference

All 6 tools, generated from https://api.unzoi.com/mcp/tools.json — the schemas the server actually accepts, not a second copy of them.

Every tool maps onto a REST endpoint, and the arguments are that endpoint's query parameters. Two argument shapes are richer than their query-string form, because a model emits them more reliably: facets is an array of strings rather than a comma-separated list, and signals is an array of {name, min, max} objects rather than the packed name:min:max syntax.

search_news

Equivalent to /search over REST.

Search the news index. Returns ranked articles with image, topics, entities, locations, and versioned industry/business/risk language signals. Supports keyword, semantic, or hybrid ranking, exact metadata filters, numeric signal ranges, pagination, and facets.

list_stories

Equivalent to /stories over REST.

Search and collapse results into deduplicated stories (one real event across many outlets). Returns story_id, article count, outlet count, and a representative headline.

top_headlines

Equivalent to /top-headlines over REST.

Most-recent articles, optionally filtered by indexed article metadata and time range.

get_article

Equivalent to /doc/{id} over REST.

Fetch a single article's rich metadata by id, including names, structured locations and dates, quotations, amounts, related media, links, and alternate URLs.

find_related

Equivalent to /similar/{id} over REST.

Find articles semantically similar to a given article id (More-Like-This). Returns distinct related stories (deduplicated across outlets), excluding the seed article.

account_status

Equivalent to /account over REST.

Report this session's account: plan, per-minute rate limit, monthly quota and how much of it is used, whether the key stops at its quota or bills overage, how far back the plan may query (history_days; null = the full archive), calls made this session, and whether metered billing is active.

FREE: this tool is not billed against your quota in any way you would notice, and it is how to plan a time range instead of discovering the archive boundary by getting fewer results than you expected.

Takes no arguments.

Calling one directly

Nothing about this is special — it is JSON-RPC over one POST:

curl -s -X POST https://api.unzoi.com/mcp \
  -H "x-api-key: $UNZOI_KEY" \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list_stories",
      "arguments": { "q": "semiconductor export controls", "limit": 5 }
    }
  }'

The result is a content block whose text is the JSON payload — the same body GET /stories returns. See Transport for the handshake, and Errors for what a refusal looks like.