Skip to main content
Glama
ProfessionalWiki

mediawiki-mcp-server

by ProfessionalWiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-page

Read-onlyIdempotent

Fetch a single wiki page as wikitext, HTML, or metadata. Retrieve revision ID, page size, and section outline, or request a specific section to bypass truncation.

Instructions

Returns a single wiki page (wikitext source, rendered HTML, or metadata only). If the title does not exist, an error is returned. Use metadata=true to retrieve the revision ID (for edit-conflict detection), page size, and section outline. Set content="none" to fetch only metadata. Large content is truncated at 75000 bytes by default, with a marker reporting how much of it was returned and which sections a narrower read can target; a follow-up call with section=N fetches a specific section. For more than one page at a time, use get-pages. For a specific historical revision, use get-revision.

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.
titleYesWiki page title
contentNoType of content to returnsource
sectionNoSection number (0 = lead; 1..N = heading sections). Narrows content to one section.
metadataNoWhether to include metadata (page ID, revision info, size, section outline) in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+}
  3. Addedv1.0.2
  4. Removedv1.0.1
  5. Changed5 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / content / default
      Previous value: -"noContent"New value: +"source"
    • changedInput schema / properties / content / description
      Previous value: -"Format of the page content to retrieve"New value: +"Type of content to return"
    • changedInput schema / properties / content / enum
      Previous value: -[
-  "noContent",
-  "withSource",
-  "withHtml"
-]New value: +[
+  "source",
+  "html",
+  "none"
+]
    • addedInput schema / properties / metadata
      Added value: +{
+  "default": false,
+  "description": "Whether to include metadata (page ID, revision info, license) in the response",
+  "type": "boolean"
+}
  6. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate read-only and idempotent behavior, but the description adds significant behavioral detail: error on nonexistent title, truncation at 75000 bytes with a marker, and the ability to narrow to a section. This exceeds the annotation information without 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?

The description is detailed but efficiently organized: it leads with the core function, then explains parameters and alternatives in logical order. Every sentence adds useful information for the agent, with no meaningless fluff.

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 the tool's complexity (multiple content types, metadata, truncation, sections, and sibling alternatives), the description covers all essential aspects: error behavior, truncation mechanics, follow-up calls, and when to use sibling tools. There is no output schema, but the description gives enough information about what the agent will receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover all 5 parameters, but the description adds valuable semantic context: explains that metadata=true retrieves revision ID for edit-conflict detection, page size, and section outline; content='none' fetches only metadata; section=N narrows content. This goes beyond the schema's basic parameter descriptions.

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 'Returns' and resource 'single wiki page', and explicitly differentiates from get-pages and get-revision by naming them. It also clarifies content types (wikitext, HTML, metadata) and error behavior for nonexistent titles.

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 usage context: when to use metadata=true, content='none', section=N, and clearly states 'For more than one page at a time, use get-pages' and 'For a specific historical revision, use get-revision', providing direct alternative routing.

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