mediawiki-mcp-server

Overview Schema Source Related Servers Discussions Admin

mediawiki_list_pages

Read-only

List wiki pages, optionally filtered by title prefix or namespace. Use to browse existing pages, retrieve page titles and IDs, and paginate through results.

Instructions

List wiki pages with optional prefix filter.

USE WHEN: User asks "list all pages", "show pages starting with API", "what pages exist".

NOT FOR: Finding pages by content (use mediawiki_search).

PARAMETERS:

prefix: Filter by title prefix (optional)
namespace: Namespace ID (default 0 = main)
limit: Max pages (default 50)
continue_from: Pagination token from previous response

RETURNS: Page titles and IDs.

Input Schema

Name	Required	Description
`limit`	No	Maximum pages to return (default 50, max 500)
`prefix`	No	Filter pages starting with this prefix
`namespace`	No	Namespace ID (0=main, 1=talk, etc.)
`rationale`	No	Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
`continue_from`	No	Continue token for pagination

Output Schema

Name	Required	Description	Default
`pages`	Yes
`has_more`	Yes
`total_count`	No
`continue_from`	No
`returned_count`	Yes
`total_estimate`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile is covered. The description adds only that continue_from is a 'pagination token from previous response', which is useful but duplicated in the schema. It does not explain why idempotentHint=false for a read operation (enumeration may change between calls) or any rate/size behavior beyond the default limit.

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?

Well front-loaded: the one-line purpose comes first, then WHEN/NOT-FOR routing, then params and returns. The PARAMETERS and RETURNS sections are partly redundant with the input schema and output schema, which costs it a point, but the layout is scannable and free of filler prose.

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?

Since an output schema exists, the brief RETURNS line is a bonus rather than a requirement, and the routing guidance is complete for a listing tool. Minor gaps: no note on namespace id range/semantics or that large listings should be paged, though continue_from and the default limit are surfaced.

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 baseline is 3. The PARAMETERS block largely restates the schema (prefix, namespace, limit, continue_from) and omits actual schema detail such as 'max 500' and the namespace examples (0=main, 1=talk). No added semantics beyond what the schema already provides.

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+resource (list wiki pages) with the scoping modifier (optional prefix filter), and explicitly disambiguates from the closest sibling: 'NOT FOR: Finding pages by content (use mediawiki_search).' An agent can distinguish this from the ~40 sibling tools without opening a 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?

Gives concrete USE WHEN trigger phrases ('list all pages', 'show pages starting with API') plus an explicit NOT FOR with the named alternative (mediawiki_search). Both the positive and negative routing conditions are covered.

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

Deploy Server