Skip to main content
Glama
ProfessionalWiki

mediawiki-mcp-server

by ProfessionalWiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search-page

Read-onlyIdempotent

Search wiki page titles and full-text content for specified terms. Returns matching pages with snippets, size, timestamp, and namespace, with optional namespace filtering and result limit.

Instructions

Searches wiki page titles and page content (full-text) for the provided terms. Returns matching pages with a snippet, size, timestamp, and the namespace the match came from. Covers the namespaces the wiki counts as content unless namespaces names the namespace IDs to search; get-site-info lists a wiki's namespaces and flags which of them hold content. Accepts up to 100 matches per call (default 10); additional matches beyond the cap are flagged in the response — narrow the query to surface more. For title-prefix lookup (e.g. autocomplete), use search-page-by-prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wikiNoWiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.
limitNoMaximum number of search results to return
queryYesSearch terms
namespacesNoNamespace IDs to search — e.g. [0, 12] for main and help

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.0
    • addedInput schema / properties / namespaces
      Added value: +{
+  "description": "Namespace IDs to search — e.g. [0, 12] for main and help",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "minItems": 1,
+  "type": "array"
+}
  2. Changed1 schema field changedv0.15.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / wiki
      Added value: +{
+  "description": "Wiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.",
+  "type": "string"
+}
  4. Addedv1.0.2
  5. Removedv1.0.1
  6. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of search results to return (1-100)"New value: +"Maximum number of search results to return"
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  7. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description does not contradict them. Beyond that, it adds substantial behavioral context: the full-text vs title scope, the default of 10 and hard cap of 100 with overflow flagging, and the namespace-scope fallback to content namespaces. This exceeds what the annotations alone convey and there is no annotation contradiction.

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?

Four dense sentences, each earning its place: purpose+returns, namespace scoping, limit/cap behavior, and sibling routing. The core function is front-loaded and the alternative-tool note is placed last where it reads naturally. The only minor blemish is the awkward phrase 'unless namespaces names the namespace IDs', but it remains intelligible and costs no real clarity.

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?

For a search tool with no output schema, the description compensates by describing the return contract (matching pages with snippet, size, timestamp, namespace). It covers scope, defaults, caps, and the sibling alternative. Given the schema is fully self-documenting for parameter types and the annotations carry the safety profile, nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description adds value on top: it reveals the default limit of 10 not present in the schema, explains the cap-flagging behavior for the limit parameter, and clarifies that omitting namespaces means 'content namespaces' — a semantic the schema alone does not state. It doesn't fully document each parameter, but it meaningfully augments the schema rather than repeating it.

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?

The description states a specific verb and resource: 'Searches wiki page titles and page content (full-text) for the provided terms.' It also enumerates what is returned (snippet, size, timestamp, namespace), which makes the purpose concrete and self-contained. It explicitly distinguishes itself from search-page-by-prefix, so an agent can separate the two sibling tools without opening either schema.

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?

The description gives explicit routing guidance: 'For title-prefix lookup (e.g. autocomplete), use search-page-by-prefix.' It also explains when to narrow a query (when matches exceed the cap), how namespace scope is determined, and where to resolve namespaces (get-site-info). This is explicit when-to-use and when-not-to-use guidance with named alternatives.

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