Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia page links

wikipedia_page_links_list
Read-onlyIdempotent

Lists a Wikipedia page's internal links, external URLs, templates, categories, or interwiki links to map references and page structure. Use the title and link type to retrieve paginated results.

Instructions

List a Wikipedia page's internal links, external URLs, templates, categories or interwiki links. Requires title. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
typeNoWhich links: `internal`, `external` URLs, `templates`, `categories` or `interwiki`. Default: `internal`.internal
limitNoRows per page, 1 to 500. Default: 50.
titleYesRequired. Page title on the chosen edition, e.g. `Albert Einstein`, `C++` or `Talk:Barack Obama`. URL-encode it in the path.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
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.8/5.0
Behavior4/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 structurally. The description adds the pending behavior an agent actually needs to drive the call correctly: the result is a paged list and the cursor is the continuation mechanism. It does not state a default page size or result ordering, which keeps it from a 5.

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?

Two short sentences, purpose first, prerequisite and return/pagination note after — no filler, no repetition of the title, and nothing an agent must read twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter read-only list tool with fully covered schema descriptions and no output schema, the description covers what the tool does, what is mandatory, and how to paginate. The only omission is the shape of an individual link record, which is minor for a list-of-links endpoint.

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 every parameter (lang, type enum, limit, title, cursor, plus the context/llm_model/conversation_id fields) is already documented in the schema. The description only restates the required `title` and the link-type set, adding no semantics beyond what the enum and property descriptions provide; 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?

States a specific verb ('List') and resource ('a Wikipedia page's ... links') and enumerates the five link categories the `type` parameter selects, so the agent knows exactly what comes back. It stops short of differentiating itself from the closely related sibling wikipedia_page_backlinks_list (links *to* a page), which is the one confusion risk here.

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?

Provides one useful prerequisite ('Requires `title`') and a pagination cue ('use cursor when paginated'), but gives no when-to-use vs. when-not guidance and never points to an alternative such as backlinks_list for reverse links. Usage is implied by the enumerated link types rather than stated.

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