Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google News topic or publisher id

google_news_topic_resolve
Read-onlyIdempotent

Resolve a place, section, MID, or name into Google News topic and publisher IDs. Use it to find the correct topic identifiers before fetching news for that topic.

Instructions

Get Google News topic or publisher ids matching a place, section, MID or name. Optional inputs: language, country, place, section, mid and 1 more.

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_topic_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
midNoKnowledge Graph MID to resolve, e.g. `/m/09nm_`.
placeNoPlace name to resolve, e.g. `London` or `San Francisco, CA`.
queryNoName to resolve through Google News suggestions, e.g. `Taylor Swift` or `Reuters`. Matches are noisy; the candidates are 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.
sectionNoSection name to resolve: `WORLD`, `NATION`, `BUSINESS`, `TECHNOLOGY`, `ENTERTAINMENT`, `SPORTS`, `SCIENCE` or `HEALTH`.
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.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so a lower bar applies. The description adds nothing beyond that: no return shape, no indication that matches are noisy and multiple candidates come back, no auth or error behavior. The one genuinely useful behavioral note (noisy matches) lives in the schema, not the description.

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

Conciseness3/5

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

Short and front-loaded, with the core action stated first. The second sentence duplicates schema-listed parameters and ends with an unhelpful "and 1 more", which is padding rather than information.

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 resolver with 9 parameters, no output schema and unusual required fields (`context`, `llm_model`), the description never says what is returned or how the resolved ids feed the sibling article tools. The schema carries most of the load, so it is workable but not complete.

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 every parameter, including the pattern for `mid`, the enum for `section`, and the language/country pairing rule. The description only re-enumerates optional inputs and truncates at "and 1 more", so it adds 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?

Uses a specific verb and resource: "Get Google News topic or publisher ids" resolved from a place, section, MID or name. That is enough to tell it apart from sibling listing tools such as google_news_topic_articles_list, though no sibling is named. The trailing "and 1 more" leaves the input set fuzzily stated, which keeps it short of a 5.

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?

Usage is only implied: an agent must infer that this is the id-resolution step that precedes the article-list tools. There is no explicit when-to-use, when-not-to-use, or named alternative, and nothing says whether the caller should prefer `query` over `place`/`mid`.

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