Skip to main content
Glama

mediawiki_list_pages

Read-onlyIdempotent

Retrieve a list of wiki pages filtered by title prefix or namespace. Provides page titles and IDs for navigation and management.

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

TableJSON Schema
NameRequiredDescriptionDefault
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
prefixNoFilter pages starting with this prefix
namespaceNoNamespace ID (0=main, 1=talk, etc.)
limitNoMaximum pages to return (default 50, max 500)
continue_fromNoContinue token for pagination

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagesYes
returned_countYes
total_countNo
total_estimateNo
has_moreYes
continue_fromNo
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint, confirming safe read behavior. The description adds value by explaining pagination via continue_from and stating returns of page titles and IDs, but does not elaborate on rate limits or other side effects beyond annotations.

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?

The description is concise, well-structured with sections for usage, parameters, and returns. Every sentence serves a purpose without redundancy, and the purpose is front-loaded.

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?

Given the tool has 5 optional parameters, full schema coverage, and an output schema, the description adequately covers pagination and return format. It could be slightly more explicit about pagination iteration, but overall it provides sufficient context for correct invocation.

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 coverage is 100% with all parameters described. The description restates parameter info in a bullet list, adding marginal value with reminders of defaults (e.g., default 50 for limit), but does not introduce new semantics beyond the schema.

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 clearly states 'List wiki pages' with specific verb and resource, and distinguishes from the sibling tool 'mediawiki_search' by explicitly noting it is not for finding by content. This provides precise purpose differentiation.

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 includes explicit 'USE WHEN' and 'NOT FOR' sections, giving concrete examples like 'list all pages' and directing to alternatives for content search. This provides clear guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olgasafonova/mediawiki-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server