SerpKite

Google News

news

Read-onlyIdempotent

Search Google News for recent articles. 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "news"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search query
`page`	No
`time`	No	Restrict to recent results
`engine`	No	google (default), auto (fall back to other engines when Google is unavailable), or brave, bing, yahoo, duckduckgo; a comma-separated list also works
`country`	No	Country code, e.g. us, de, ru
`end_date`	No	Only results published on or before this date (YYYY-MM-DD)
`language`	No	Language code, e.g. en, ru (Russian). Does not change country
`location`	No	City-level location, e.g. "Austin, Texas, United States"
`start_date`	No	Only results published on or after this date (YYYY-MM-DD)
`boost_domains`	No	Move results from these sources to the top, keeping the rest: a domain (example.com, subdomains match), a path prefix (github.com/org) or a TLD (.gov)
`exclude_domains`	No	Drop results from these sources: a domain (example.com, subdomains match), a path prefix (github.com/org) or a TLD (.gov)
`include_domains`	No	Only results from these sources: a domain (example.com, subdomains match), a path prefix (github.com/org) or a TLD (.gov)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / country / description

Previous value: -"Country code, e.g. us, de, ru. Uses shared proxy routes"New value: +"Country code, e.g. us, de, ru"

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / engine / description

Previous value: -"google (default), auto (fall back to other engines when Google is unavailable), or brave, bing, yahoo, duckduckgo, mojeek; a comma-separated list also works"New value: +"google (default), auto (fall back to other engines when Google is unavailable), or brave, bing, yahoo, duckduckgo; a comma-separated list also works"

First observedOct 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and idempotency are covered. The description adds genuinely useful cost context ("1 credit"), but says nothing about result shape, pagination limits, or the engine-fallback behavior exposed by the `engine` parameter.

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

Conciseness5/5

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

Two short sentences with zero waste; the core capability is front-loaded and the cost note is compactly appended. Nothing could be removed without losing information.

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

Completeness3/5

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

With 12 parameters and no output schema, the description should say at least something about what comes back (article fields, result count, pagination ceiling) and how date-range vs. `time` interact. The rich schema compensates for parameter gaps, but the return-value side is entirely undocumented.

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 coverage is 92%, so the schema already documents nearly every parameter including the enum and the domain-list semantics. The description adds nothing beyond the schema; the phrase "recent articles" loosely gestures at `time`/`start_date` but provides no extra meaning. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource ("Search Google News") and scopes results to "recent articles", which distinguishes it from the general `search` and `scholar` siblings. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this over `search`, `scholar`, or `ai_mode`, and no prerequisites or exclusions. The word "News" implicitly signals the use case, but the agent must infer everything else.

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

All SerpKite 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.