Skip to main content
Glama

mediawiki_get_page_info

Read-onlyIdempotent

Retrieve a page's metadata including last edit timestamp, size, protection status, and creator. Useful for checking page history and security without fetching content.

Instructions

Get page metadata without content.

USE WHEN: User asks "when was X last edited", "who created the FAQ", "is the page protected".

NOT FOR: Getting page content (use mediawiki_get_page). Not for full edit history (use mediawiki_get_revisions).

PARAMETERS:

  • title: Page name (required)

RETURNS: Last edit timestamp, page size, protection status, creator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
titleYesPage title

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
page_idYes
namespaceYes
content_modelYes
page_languageYes
lengthYes
touchedYes
last_revision_idYes
categoriesNo
links_countYes
existsYes
redirectYes
redirect_toNo
protectionNo
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds valuable specifics about what metadata is returned (last edit timestamp, page size, protection status, creator), going 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?

Highly concise with structured sections (USE WHEN, NOT FOR, PARAMETERS, RETURNS). Front-loaded with purpose. Every sentence adds value with zero wasted words.

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?

Covers purpose, usage guidance, parameters, and return values. With annotations and output schema present, the description provides sufficient context for correct tool selection and 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 both parameters described. The description repeats 'title: Page name (required)' which adds no new meaning over the schema's 'Page title'. The optional 'rationale' parameter is not mentioned, but it's self-explanatory. Minimal value added.

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 'Get page metadata without content', uses specific verbs and resources, and distinguishes from siblings mediawiki_get_page (content) and mediawiki_get_revisions (edit history). Lists concrete use-case examples.

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?

Includes explicit 'USE WHEN' with example queries and 'NOT FOR' sections naming alternative tools. Provides clear decision criteria for when to use this tool vs siblings.

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