Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google News top stories

google_news_top_stories_list
Read-onlyIdempotent

List top-story clusters for a Google News edition, including the other outlets covering each story; set language and country to target the edition.

Instructions

List Google News top-story clusters for an edition, each with the other outlets covering it. Optional inputs: language and country. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so safety is covered. The description adds the substantive detail that results are clusters rather than articles, but says nothing about result volume, pagination, or ordering of the top-story list. Adequate but not rich beyond annotations.

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 definition is short and front-loads the resource and scope, which is good. However, the closing sentence "Returns a list." carries essentially no information and does not earn its place.

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?

For a simple read-only list tool with no output schema, the description conveys the key shape (clusters with other outlets). It omits any indication of how many stories are returned or how the required context/llm_model/conversation_id parameters relate to actually getting a usable result, which the schema carries alone.

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 both topical parameters are fully documented in the schema, including formats, defaults, and the rejection behavior for unsupported pairs. The description only restates that language and country are optional, adding no meaning beyond 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 states a specific verb and resource ("List Google News top-story clusters for an edition") and adds a distinguishing detail: each cluster includes "the other outlets covering it," which sets it apart from a plain headlines listing. It does not name which sibling to use instead, but the resource scope is clear enough to select on.

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?

There is no when-to-use guidance and no mention of alternatives such as headlines, sections, or topic articles, despite several siblings that could plausibly be confused with this one. The only hint is "for an edition," which implies regional/language scoping but not tool selection.

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