Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google News suggestions

google_news_suggest_list
Read-onlyIdempotent

Find Google News topic and publisher suggestions matching a name or query. Use them to identify relevant topics and publishers for news retrieval.

Instructions

List Google News topic and publisher suggestions matching a name. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_news_suggest_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Name to get Google News suggestions for, e.g. `Taylor Swift`.
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.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 and the bar is lower. The description adds only 'matching a name' (partial-match semantics) and 'Returns a list' — the latter is genuinely useful since there is no output schema. It says nothing about result counts, ranking, or what a suggestion object contains, so the added behavioral value is thin.

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 purpose, and no filler. The 'Requires `query`' sentence is partly redundant against a required-field schema, which is the only small waste.

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 six parameters, a rich schema and no output schema, the definition covers purpose and that a list comes back, which is the minimum an agent needs to call it. It does not describe the shape or size of the returned suggestions, nor does it route the agent away from article-oriented siblings when a full search is actually wanted.

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 baseline is 3. The description's only parameter reference ('Requires `query`') restates what the schema already marks as required and adds no new meaning. Country/language pairing, llm_model and conversation_id handling are all fully documented in the schema, so no compensation is needed.

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 topic and publisher suggestions') plus the matching condition ('matching a name'). This separates it from siblings like google_news_search_list or google_news_headlines_list, which return articles rather than autocomplete-style suggestions. It stops short of explicitly naming an alternative, but the resource is unmistakable.

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 or when-not-to-use guidance and no named alternative. The only directive is 'Requires `query`', which is a constraint, not usage guidance. An agent must infer from the sibling list that this is the typeahead/discovery call rather than the article-retrieval call.

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