Skip to main content
Glama
Sign In
google-news-mcp-server

google-news-mcp-server

by dataxplore19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Google News: search articles

search_news
Read-only

Search Google News by keywords to retrieve articles with real publisher URLs, sources, dates, and optional full text; filter by timeframe, date range, country, and language.

Instructions

Search Google News for one or more keywords and get articles with the real publisher URL, source, publication date, description and optionally the full article text. Supports a recent timeframe or a custom date range, any country and language, and more than 100 articles per keyword. Google operators work in keywords ("exact phrase", site:reuters.com, -word).

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

Input Schema

NameRequiredDescriptionDefault
regionNoCountry:language, e.g. US:en, GB:en, IN:en, FR:fr, DE:de, ES:es, BR:pt-419, JP:ja (84 pairs)US:en
date_toNoEnd date YYYY-MM-DD
keywordsYesSearch keywords
date_fromNoStart date YYYY-MM-DD
full_textNoInclude the full article text (longer answer)
timeframeNoRecent period. Ignored if date_from or date_to is set1d
max_articlesNoMax articles per keyword. Above 100 the search is split by date

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered, and the description adds genuine behavior: it discloses the exact shape of returned articles, that full_text yields longer output, and that requests above 100 articles are split by date. It says nothing about rate limits or failure modes, keeping it just short of 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.

Conciseness5/5

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

Three dense sentences, front-loaded with the action and returned data, followed by capability coverage and then the operator syntax note. No filler and nothing repeated from the schema.

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 no output schema, the description correctly compensates by enumerating returned fields, and it covers region, date-range, timeframe interaction and article-count behavior. The only gap for an agent is the absence of any guidance tying it to its sibling get_topic_news.

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, and the description earns a bump by documenting that Google operators ('exact phrase', site:, -word) are valid inside keywords and by explaining that more than 100 articles per keyword is possible. It does not add detail on region pairs or date format beyond what the schema already states.

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 opens with a specific verb and resource ('Search Google News for one or more keywords') and enumerates the returned fields (publisher URL, source, publication date, description, optional full text), so the agent knows exactly what it gets. It does not name or contrast with its sibling get_topic_news, so it falls short of full sibling differentiation.

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?

Usage is implied rather than stated: the description shows it supports timeframe or custom date ranges, any country/language, and Google operators, which signals the keyword-search use case. However, it never says when to choose this over get_topic_news or when NOT to use it, leaving the routing decision to inference.

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

Deploy Server

Other Tools