Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Wikipedia

wikipedia_search_list
Read-onlyIdempotent

Search a Wikipedia edition by query and filters to retrieve paginated results with snippets, match ranges, totals, and suggestions.

Instructions

Search a Wikipedia edition, with snippets, match ranges, totals and suggestions. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
sortNoResult order: relevance (default), create_timestamp, incoming_links, last_edit, title_natural, just_match, none or random, optionally with `_asc` or `_desc`.
limitNoResults per page, 1 to 500. Default: 50.
queryYesRequired. Search text. Operators such as `insource:`, `incategory:` and `intitle:` work. A plain `insource:/.../` regular expression can be slow; prefer words or `insource:"..."`. At most 300 characters.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters. Rankings can shift between pages, so a title can repeat at a page boundary; de-duplicate by `pageId`.
offsetNoFirst result to return, 0 to 9999. Use `cursor` to continue a walk.
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.
namespaceNoNamespace id, e.g. `0` for articles or `14` for categories.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds only that results are a paginated list. It omits the richer behavioral facts that live in the schema -- that cursors are filter-bound and that rankings shift so results can duplicate across page boundaries.

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?

Three short, front-loaded sentences with the core purpose first and pagination second. 'Requires `query`' duplicates the schema's required list, a small amount of waste, but nothing is bloated or buried.

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 10-parameter search tool with no output schema, the description is adequate but thin: it names the return fields in a phrase without indicating result shape, ranking behavior, or that ranking ties back to the `sort` parameter. The heavy schema documentation compensates for most parameter gaps, but an agent still lacks a full picture of what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the per-parameter descriptions (lang, sort pattern, limit range, cursor semantics, offset) already carry the semantics; baseline is 3. The description nudges slightly above by stating that `query` is required and by pointing at the cursor for pagination continuation, though it adds no syntax detail beyond the schema.

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 (Search) and resource (a Wikipedia edition) and enumerates the return payload (snippets, match ranges, totals, suggestions). It is clear on its own, but it does not distinguish itself from close siblings such as wikipedia_search_suggest_list, so an agent must infer the difference from the names alone.

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?

Gives a concrete calling hint ('use cursor when paginated') and flags the required `query`, which is useful operational guidance. It never says when this tool should be chosen over the suggestion-search or wikidata-search siblings, leaving the primary routing decision implicit.

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