Skip to main content
Glama
serper-search-mcp-server

serper-search-mcp-server

search_news

Search Google News for headlines, sources, and publication dates, with freshness and date-range filters for current or historical news.

Instructions

Google News search via Serper API. Returns headlines, sources, and publication dates. Defaults to past day — pass freshness="any" for historical news, or use after:/before: operators in the query for date ranges.

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": {
      "query": "<query>"
    },
    "name": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNews search query.
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
ui_langNoUI language (e.g. "en-US"). Default: "en".
freshnessNoTime filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results ("today", "this week", "latest", current year); omit or "any" for timeless or historical questions. The response footer echoes the filter that was applied. Default: "pd".
safesearchNo"off" | "moderate" | "strict". Default: "moderate".moderate
num_resultsNoResults (1–20, default 10). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".
link_resolutionNoGoogle result links beyond the top 3 may come back as google.com/goto redirects. "auto" (default): top 3 resolved, any leftover goto links get a search_id for resolve_links. "all": also resolve every link now (free, but adds ~30 s when goto links are present). "none": fastest, links exactly as Google returns them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.0
    • changedInput schema / properties / freshness / description
      Previous value: -"Time filter: pd=day pw=week pm=month py=year. Default: \"pd\"."New value: +"Time filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results (\"today\", \"this week\", \"latest\", current year); omit or \"any\" for timeless or historical questions. The response footer echoes the filter that was applied. Default: \"pd\"."
    • changedInput schema / properties / freshness / enum
      Previous value: -[
      -  "pd",
      -  "pw",
      -  "pm",
      -  "py"
      -]New value: +[
      +  "pd",
      +  "pw",
      +  "pm",
      +  "py",
      +  "any"
      +]
  2. First observedv4.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It discloses the default past-day time filter and returned fields, but it does not state that the operation is read-only, mention rate limits or credit costs, or describe pagination or broader response behavior.

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?

The description is three compact, front-loaded sentences, and every sentence adds concrete information about the search source, returned fields, and temporal filtering. There is no filler or redundant wording.

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?

For an 8-parameter search tool with complete schema descriptions and no output schema, the description provides the key return fields and temporal-filter behavior needed to call it correctly. It lacks only sibling-selection guidance and some operational details already covered by the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by mentioning after:/before: operators in the query for date ranges, which the schema does not document. It also reinforces the freshness default, while the remaining parameters are adequately documented in the schema.

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?

The description names a specific verb and resource, 'Google News search', identifies the provider, and states the returned content: headlines, sources, and publication dates. It is clear what the tool does, but it does not explicitly distinguish this news search from sibling web or image search tools.

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?

The description gives useful guidance on the freshness behavior: it defaults to the past day, and agents should pass freshness="any" or use after:/before: query operators for historical news. It does not explain when to choose this tool over sibling search tools or when not to use it.

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