Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Wikipedia pages

wikipedia_pages_batch_get
Read-onlyIdempotent

Fetch up to 20 Wikipedia pages in a single call and get each title's lookup status, so you can resolve multiple articles without separate requests.

Instructions

Get up to 20 Wikipedia pages in one call, with the lookup status of each requested title. Requires titles.

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

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
titlesYesRequired. Page titles separated by `|` (titles may contain commas), 1 to 20, e.g. `Albert Einstein|Barack Obama`. Duplicates are dropped.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.7/5.0
Behavior4/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. The description adds genuine value beyond that by disclosing that the response includes 'the lookup status of each requested title', telling the agent that missing titles are reported per-item rather than failing the whole batch. It does not mention rate limits, redirect handling, or what the page payload itself contains.

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

Conciseness5/5

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

A single sentence with the batch limit and the return characteristic front-loaded, and no filler or repetition of the title. Every clause carries 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 5-parameter batch tool with full schema coverage and rich annotations, the description covers what it does and that per-title status is returned. However, with no output schema, it never clarifies whether 'pages' means full page content, summaries, or just existence/metadata — a meaningful ambiguity given the existence of wikipedia_page_content_get. That is the main missing piece an agent would need.

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 titles, lang, context, llm_model and conversation_id in detail. The description only restates the requirement and the 20-item cap, both of which are already in the schema (required list and maxItems), adding no new parameter meaning. Baseline 3 is appropriate.

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 ... Wikipedia pages') plus a batch scope ('up to 20 ... in one call'), which implicitly contrasts with the single-page sibling. It stops short of naming wikipedia_page_get or wikipedia_page_content_get explicitly, so the agent must infer the batching distinction from the phrase 'in one call'.

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: the phrase 'up to 20 ... in one call' suggests this is the choice when many titles are needed, and 'Requires `titles`' restates the schema. There is no explicit when-to-use / when-not-to-use statement or named alternative for the single-title case.

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