Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Google News

google_news_search_list
Read-onlyIdempotent

Search Google News by keywords, operators, edition, and date range, then follow the cursor to retrieve older result pages.

Instructions

Search Google News by words, operators, edition and time window, and follow the cursor into older windows. Requires query. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_news_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNoOnly articles from this recent window, e.g. `1h`, `7d`, `1y`.
afterNoOnly articles after this date, `YYYY-MM-DD`.
queryYesRequired.
beforeNoOnly articles before this date, `YYYY-MM-DD`.
cursorNo`page.nextCursor` from the previous response. It continues the same query and edition one day at a time; do not send `when`, `after` or `before` with it.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoTwo-letter country of the edition, e.g. `US`, `GB` or `JP`. Default: `US`. Send it with `language`; an unsupported pair is rejected with every supported pair listed.
languageNoLanguage and locale of the edition, e.g. `en-US`, `de`, `pt-BR` or `zh-Hant`. Default: `en-US`. The 400 response for an unsupported pair lists every supported pair.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only that results are a list and cursor-driven paging walks backwards through windows, which is largely duplicated by the cursor schema text; no rate limits or edition-rejection behavior are mentioned.

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?

A single tight sentence, front-loaded with the verb and the searchable dimensions, followed by the pagination behavior and return shape. No wasted 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 a 10-parameter open-world search with no output schema, the description covers purpose, the required argument, and how to continue paging, which is what an agent needs to call it correctly. The remaining nuance (country/language compatibility, conversation_id echoing) is fully handled in the schema.

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%, so every parameter — including `when`, `after`, `before`, `cursor`, `country`/`language` pairing — is already documented in the schema. The description restates only that `query` is required, adding nothing beyond structured data, so 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 (Search) and resource (Google News) plus the searchable facets: words, operators, edition, time window. It implicitly separates itself from headline/section/topic siblings by emphasizing free-text query search, though it never names an alternative.

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

Usage Guidelines4/5

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

Gives the key usage rule for pagination — 'follow the cursor into older windows' — and notes `query` is required. It does not explicitly contrast with siblings like headlines_list or suggest_list, so an agent must infer when keyword search is preferred over browsing.

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