Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google News home briefing

google_news_home_get
Read-onlyIdempotent

Fetch Google News home briefing articles and navigation sections for a chosen language and country, enabling localized news summaries and dashboards.

Instructions

Get Google News home briefing articles with the edition's navigation sections. Optional inputs: language and country.

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_home_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.
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description still adds real value by disclosing what the response contains — briefing articles plus the edition's navigation sections — which matters because there is 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?

Two short sentences, with the core capability front-loaded before the input note. The trailing 'Optional inputs: language and country' sentence largely duplicates the schema and does not fully enumerate the actual parameters, so it earns only marginal place.

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 read-only retrieval tool with no output schema and a fully documented 5-parameter schema, the description covers the essentials: what is fetched and what the response includes. It stops short of describing pagination, article counts, or the shape of the navigation sections, which an agent might reasonably want.

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 the schema already explains language, country, context, llm_model, and conversation_id in detail, including the unsupported-pair 400 behavior. The description only echoes that language and country are optional and adds no syntax, defaults, or pairing constraints 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 names a specific verb and resource ('Get Google News home briefing articles') plus a distinguishing output element ('with the edition's navigation sections'). That separates it in spirit from sibling list tools such as google_news_headlines_list or google_news_top_stories_list, though it never names a sibling to contrast with 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?

There is no guidance on when to choose this home-briefing tool over the many other Google News retrieval siblings (headlines, top stories, topic articles, search). The only context offered is a restatement of the optional language/country inputs, which the schema already documents.

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