Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google News Full Coverage story

google_news_story_get
Read-onlyIdempotent

Retrieve a Google News Full Coverage story and its articles from multiple outlets by storyId to compare how different sources report the same event.

Instructions

Get Google News Full Coverage story and articles from different outlets. Requires storyId.

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

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.
storyIdYesRequired. Google News Full Coverage story id, e.g. `CAAqNggKIjBDQklTSG...`.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful output hint that results include articles from multiple outlets (valuable since there is no output schema), but says nothing about pagination, result limits, or edition/language behavior.

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?

Two short sentences with no wasted words and the core action front-loaded. The second sentence mostly repeats the schema's required-field constraint, which slightly limits its value.

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 fetch of a single story this is serviceable: it says what is returned and what is needed. But with no output schema, it could say more about the shape of the returned story/articles and the country/language edition effects that the schema only partially covers.

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 country/language pairing rules and conversation_id sequencing, are documented in the schema. The description only restates that storyId is required, adding no meaning beyond the schema; 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 and resource: retrieves a Google News Full Coverage story plus articles from different outlets, and notes the required storyId. It is clear what the tool returns, though it does not differentiate itself from nearby siblings such as google_news_articles_resolve or the various *_list tools.

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

Usage Guidelines3/5

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

'Requires `storyId`' implies a prerequisite (you must already have a story id, presumably from a search or list call), but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is only implied.

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