SerpMCP

Search Google News

serp_google_news

Read-only

Search Google News for articles and retrieve structured results with pagination, country, language, and time-range filters to find relevant news quickly.

Instructions

Search Google News and get news article results.

Performs a Google News search and returns structured news results.

Input Schema

Name	Required	Description
`page`	No	Page number for pagination (default: 1).
`query`	Yes	The search query string for news search. Required.
`number`	No	Number of results per page (default: 10). Note: More than 10 results may incur additional credits.
`country`	No	Country code for localized results (e.g., 'us', 'cn', 'uk'). Default is 'us'.
`language`	No	Language code for results (e.g., 'en', 'zh-cn', 'fr'). Default is 'en'.
`time_range`	No	Time filter for results. Options: 'h'/'qdr:h' (past hour), 'd'/'qdr:d' (past day), 'w'/'qdr:w' (past week), 'm'/'qdr:m' (past month), 'y'/'qdr:y' (past year), or None for no time restriction (default).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.1.49Aug 11, 2026

changedInput schema / properties / country / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 32,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / language / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 32,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / number / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / page / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / query / maxLength
```
Added value: +2048
```
addedInput schema / properties / query / minLength
```
Added value: +1
```
addedInput schema / properties / query / pattern
```
Added value: +".*\\S.*"
```

changedInput schema / properties / time_range / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "h",
+      "d",
+      "w",
+      "m",
+      "y",
+      "qdr:h",
+      "qdr:d",
+      "qdr:w",
+      "qdr:m",
+      "qdr:y"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / time_range / description

Previous value: -"Time filter for results. Options: 'qdr:h' (past hour), 'qdr:d' (past day), 'qdr:w' (past week), 'qdr:m' (past month), or None for no time restriction (default)."New value: +"Time filter for results. Options: 'h'/'qdr:h' (past hour), 'd'/'qdr:d' (past day), 'w'/'qdr:w' (past week), 'm'/'qdr:m' (past month), 'y'/'qdr:y' (past year), or None for no time restriction (default)."

Addedv0.1.46May 31, 2026
Removedv0.1.45May 24, 2026
First observedv0.1.0Feb 6, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint, so the safety profile is covered. The description adds no behavioral context of its own — no mention of credit costs (which the schema's `number` param hints at), rate limits, or how open-world results behave.

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

Conciseness3/5

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

Very short, but the second sentence is pure redundancy of the first, so it fails the "every sentence earns its place" test. Not verbose, just non-informative.

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 full schema descriptions, annotations and an output schema, the structured data covers most of what an agent needs. The description is adequate but contributes nothing toward disambiguating this vertical from its many siblings.

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% with per-parameter descriptions for query, number, country, language and time_range, so the schema carries the semantics. The description adds nothing, leaving it at the baseline.

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

Purpose3/5

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

The verb+resource ("Search Google News") is clear, but the second sentence merely restates it as "structured news results." Nothing distinguishes it from siblings like serp_google_search or serp_google_videos beyond the word "News."

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?

No guidance on when to choose this over serp_google_search or other verticals, and no mention of query construction or time_range usage patterns. The agent must infer selection from the tool name alone.

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

Deploy Server