Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google News publisher articles

google_news_publisher_articles_list
Read-onlyIdempotent

Retrieve articles from a Google News publisher using its publication ID, including URLs, images, authors, and labels for research and monitoring.

Instructions

List Google News publisher articles with publisher URLs, images, authors and labels. Requires publicationId. 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": {
      "publicationId": "<publicationId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_news_publisher_articles_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.
publicationIdYesRequired. Google News publication id, from the `topics/resolve` endpoint or an article record's `source.publicationId`.
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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the shape of each returned item and confirms the return is a list, but says nothing about pagination, result caps, ordering, or rate limits for a read-only listing endpoint.

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, front-loaded with the action and payload fields, with no filler. It is close to the minimum needed, though the trailing "Returns a list" is near-redundant with the verb "List".

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 read-only list tool with a fully described schema and no output schema, the definition is adequate but thin: it never covers pagination, page size, or the fact that output items are structured article records. Nothing is misleading, but an agent cannot predict result volume or how to page.

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 all six parameters (including the context/llm_model/conversation_id plumbing) are documented in the schema itself. The description repeats the `publicationId` requirement without adding format or sourcing detail beyond the schema's own note about `topics/resolve`.

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 and resource ("List Google News publisher articles") plus the fields returned (publisher URLs, images, authors, labels), which separates it from generic article search/headline siblings. The required `publicationId` reinforces that this is a per-publisher listing, though the description never says so explicitly.

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 signal is "Requires `publicationId`", which is a constraint rather than guidance. It does not say when to pick this over `google_news_topic_articles_list`, `google_news_search_list`, or `google_news_headlines_list`, nor what prerequisites exist (e.g., resolving a publication id first).

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