Google Search MCP Server

news_monitor

Monitor news for a specific topic and receive alerts from chosen sources. Set language, country, and date restrictions to filter results.

Instructions

Monitor news and get alerts for specific topics

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": {
      "topic": "<topic>"
    },
    "name": "news_monitor"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes	Topic to monitor
`sources`	No	News sources to monitor (e.g., ["bbc.com", "cnn.com", "reuters.com"])
`language`	No	Language code (e.g., "en", "es")	en
`country`	No	Country code (e.g., "us", "uk")	us
`maxResults`	No	Maximum results to return
`dateRestrict`	No	Date restriction for news	d7

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 30, 2026

TDQS

C2.3/5.0

Behavior1/5

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

No annotations provided, and the description fails to disclose critical behaviors: does it continuously monitor or perform a single query? Does it actually send alerts or just return results? This is a significant gap.

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?

The description is short (one sentence), but it is vague and could be more precise. It front-loads the main idea but lacks necessary details.

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

Completeness2/5

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

With 6 parameters and no output schema or annotations, the description is insufficient. It does not clarify the return format, continuous vs one-time behavior, or how 'alerts' work, leaving significant ambiguity for the agent.

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 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; it merely restates the tool's purpose without explaining parameter relationships or usage nuances.

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 description states the tool monitors news and gets alerts, but 'monitor' implies continuous polling while the schema suggests a one-time query with maxResults and dateRestrict. The purpose is vaguely clear but lacks specificity and differentiation from sibling tools like google_search.

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 use this tool versus alternatives (e.g., google_search for general news, academic_search for scholarly). No scenarios or exclusions are mentioned.

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

Deploy Server