Skip to main content
Glama

get-pages

Read-onlyIdempotent

Fetch multiple wiki pages in a single call, returning wikitext source or metadata. Supports up to 50 titles with inline missing page reports and content truncation. Use for batch reading, diffing, or syncing pages locally.

Instructions

Returns multiple wiki pages in one call (wikitext source or metadata only). Suited to reading a cluster of related pages, diffing a page family, or syncing pages to local storage. Accepts up to 50 titles; missing pages are reported inline (not as errors). Each page's content is truncated at 50000 bytes by default with a trailing marker listing available sections; get-page with section=N fetches a specific section. For a single page or HTML output, use get-page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titlesYesArray of wiki page titles (1..50)
contentNoType of content to return; "none" returns metadata onlysource
metadataNoWhether to include metadata (page ID, revision info) in the response
followRedirectsNoFollow wiki redirects. When true (default), redirect targets are returned with a "Redirected from:" line in the metadata. Set false to fetch redirect pseudo-pages as-is (sync-fidelity).
Behavior5/5

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

Annotations provide safety hints (readOnly, idempotent). Description adds key behaviors: missing pages reported inline, 50000-byte truncation with section marker, and redirect handling details.

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 sentences, front-loaded with purpose, no redundant information. Every sentence adds value.

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?

Given 4 parameters, no output schema, and rich annotations, the description covers purpose, usage, limits, edge cases (missing pages, truncation, redirects), and sibling references. Fully complete for this tool type.

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 has 100% coverage, so baseline is 3. Description adds value beyond schema: explains content='none' for metadata-only, followRedirects behavior with sync-fidelity context, and titles limit (50).

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 it returns multiple wiki pages with wikitext source or metadata. It uses specific verbs ('Returns') and resources ('wiki pages'), and distinguishes from siblings like get-page.

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?

Explicitly lists use cases ('reading a cluster of related pages, diffing a page family, syncing pages to local storage') and directs to get-page for single pages or HTML output.

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/ProfessionalWiki/MediaWiki-MCP-Server'

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