Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google News article links

google_news_articles_resolve
Read-onlyIdempotent

Resolve up to ten Google News article IDs into publisher URLs, helping identify the original publisher behind each article.

Instructions

Get publisher URLs for up to ten Google News article ids. Requires ids.

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

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Article ids, comma-separated, 1 to 10. Duplicates are dropped.
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
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that: the ten-id cap and required `ids` are both already in the schema, and it says nothing about unresolvable ids, result ordering, or batching/rate 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 the core action front-loaded and no filler. The second sentence ('Requires `ids`') is mildly redundant with the schema's required list, which is the only wasted element.

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, three of them required, and no output schema, the description should at least sketch the return shape and edge cases. 'Publisher URLs' hints at the return value, but ordering, per-id failure behavior and the reason for the context/conversation_id requirements are left entirely to the schema.

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%, with rich per-parameter documentation for ids, country/language pairing, context, llm_model and conversation_id, so the schema carries the parameter burden. The description only restates the `ids` cardinality, adding no syntax or format meaning beyond it.

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 concrete verb and resource ('Get publisher URLs') plus the input type ('Google News article ids'), which is materially different from sibling list/search tools. It does not explicitly contrast itself with siblings such as google_news_story_get or google_news_publisher_articles_list, so an agent must infer that this is the id-to-URL resolution step.

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 `ids`' states a prerequisite, and the phrase 'as returned by another endpoint' (in the schema) implies this is a follow-up call. There is no explicit when-to-use/when-not guidance, no statement about what to do when resolution fails, and no named alternative for fetching article content rather than links.

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