mediawiki-mcp-server

Overview Schema Source Related Servers Discussions Admin

mediawiki_search

Read-only

Search the wiki for pages containing specific text to find where topics are documented, returning titles, snippets, and relevance scores.

Instructions

Search ACROSS the entire wiki for pages containing specific text.

USE WHEN: User asks "find pages about X", "where is X documented", "search for X", or doesn't know which page contains information.

NOT FOR: Searching within a specific known page (use mediawiki_search_in_page instead).

PARAMETERS:

query: Search text (required)
limit: Max results (default 20)

RETURNS: Page titles, snippets with highlights, and relevance scores.

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return (default 20, max 500)
`query`	Yes	Search query text
`offset`	No	Offset for pagination
`rationale`	No	Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

Name	Required	Description	Default
`query`	Yes
`results`	Yes
`has_more`	Yes
`total_hits`	Yes
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.36.0Oct 15, 2026
- addedOutput schema / properties / results / items / properties / url
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedv1.31.0May 14, 2026

addedInput schema / properties / rationale

Added value: +{
+  "description": "Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.",
+  "type": "string"
+}

First observedMar 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover safety (readOnlyHint, openWorldHint, idempotentHint=false), and the description adds the global search scope plus a RETURNS summary of titles, highlighted snippets, and relevance scores. It does not mention pagination behavior or result caps, which offsets the otherwise strong disclosure.

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?

Header-block structure (USE WHEN / NOT FOR / PARAMETERS / RETURNS) is easy to scan and front-loads the scope and routing information. The PARAMETERS and RETURNS blocks partially duplicate the schema and output schema, costing some density.

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

Completeness5/5

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

With an output schema present, the description need not detail return values, and annotations cover the safety profile; the remaining pieces an agent needs (scope, when to use, alternative) are all present.

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 all four parameters, and the description restates only query and limit while omitting offset and rationale. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (entire wiki) with the explicit scope 'ACROSS the entire wiki', which immediately separates it from page-scoped siblings. The alternative mediawiki_search_in_page is also named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes explicit USE WHEN triggers ('find pages about X', unknown page location) and an explicit NOT FOR clause routing known-page searches to mediawiki_search_in_page. This is textbook when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server