Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google News topic articles

google_news_topic_articles_list
Read-onlyIdempotent

List articles from a Google News topic, tab, or publisher, returning publisher URLs, images, authors, and Full Coverage story IDs so you can collect structured news coverage.

Instructions

List Google News topic, tab or publisher articles with publisher URLs, images, authors and Full Coverage story ids. Requires topicId. 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": {
      "topicId": "<topicId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_news_topic_articles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoSub-tab id from `topic.tabs[].id` (for example Sports' NFL tab). Without it the topic's latest stream is returned.
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.
topicIdYesRequired. Google News topic id, from the `topics/resolve` endpoint, a section id or an article record.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description contributes the return shape (a list with publisher URLs, images, authors, Full Coverage story ids), but says nothing about pagination, result caps, or the conversation_id handshake the schema demands before parallel calls — notable gaps for a listing tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three short sentences with the capability and return fields front-loaded, then the required-parameter constraint. No filler, though 'Returns a list' is nearly redundant after 'List ... articles'.

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?

With no output schema and seven parameters, the description should cover pagination/limits and how the tab vs default stream behaviour affects results. It covers the return field set adequately but leaves an agent unable to predict result size or page through results.

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%, including detailed notes on tab fallback, country/language pairing, and the conversation_id echo rule, so baseline is 3. The description only restates that topicId is required and adds no syntax or format 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?

States a specific verb (List) and resource (Google News topic articles) and enumerates the returned fields (publisher URLs, images, authors, Full Coverage story ids). It is clear what the tool does, but the phrase 'or publisher articles' blurs the boundary with the sibling google_news_publisher_articles_list, and no sibling is named to disambiguate.

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?

The only usage constraint offered is 'Requires `topicId`'; there is no statement of when to choose this over google_news_search_list, google_news_headlines_list, or google_news_publisher_articles_list. The claim that it lists 'publisher articles' actively muddies the boundary with a dedicated sibling instead of resolving it.

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