Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia page content

wikipedia_page_content_get
Read-onlyIdempotent

Fetches a Wikipedia page's plain-text lead, rendered HTML, or wikitext by title, including sections, links, categories, templates, and media for research and content extraction.

Instructions

Get a Wikipedia page's plain-text lead, rendered HTML or wikitext, with sections, links, categories, templates and media. Requires title.

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

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
titleYesRequired. Page title on the chosen edition, e.g. `Albert Einstein`, `C++` or `Talk:Barack Obama`. URL-encode it in the path.
formatNo`text` for the plain-text lead (no lists or tables), `html` for the rendered article, `wikitext` for the source. Default: `text`.text
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
sectionNoHTML section number to return instead of the whole article.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful scope detail by saying what the payload contains (sections, links, categories, templates, media) and that `title` is required, but says nothing about missing/redirected pages, payload size, or whether `section` narrows output.

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 tight sentences, front-loaded with the capability and payload before the requirement. The trailing 'Requires `title`.' mostly duplicates the schema's required list, a small redundancy but not harmful.

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 no output schema, the description partially compensates by listing returned elements, but it does not describe the shape of the response for each format (e.g. whether html includes the full document) or behavior on missing pages. For a 7-parameter read tool this is workable but leaves gaps an agent would want filled.

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 documents lang, title, format, section, context, llm_model and conversation_id. The description only restates the `title` requirement and the format name, adding no syntax or defaulting information beyond the structured fields; 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?

Names a specific verb and resource (get a Wikipedia page's content) and enumerates the three output formats and the payload elements included, which separates it from the surrounding list/metadata siblings. It stops short of naming a sibling it is not, so an agent must still infer the boundary against e.g. wikipedia_page_get.

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 description makes clear this is the tool for retrieving page body content, but gives no explicit when-to-use/when-not or pointers to alternatives such as wikipedia_page_get for metadata or wikipedia_page_links_list for links alone. Adequate but with a clear routing gap.

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