Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_batch_get_pages_info

Read-only

Fetch metadata for multiple MediaWiki pages in a single call. Get size, last edit, categories, and protection status for up to 50 pages without retrieving their content.

Instructions

Get metadata for MULTIPLE pages in a single API call.

USE WHEN: You need info (last edit, size, categories) for 2+ pages without their content.

NOT FOR: Single page (use mediawiki_get_page_info). Not for content (use mediawiki_batch_get_pages).

PARAMETERS:

  • titles: Array of page titles (required, max 50)

RETURNS: Metadata (size, last edit, categories, protection) per page. Missing pages reported with exists=false.

Input Schema

NameRequiredDescriptionDefault
titlesYesList of page titles to get info for (max 50)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

NameRequiredDescriptionDefault
pagesYes
total_countYes
exists_countYes
missing_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.31.0
    • 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"
+}
  2. Addedv1.30.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint, so the safety profile is covered. The description adds real behavioral detail beyond them: the 50-item batch ceiling and the exists=false convention for missing pages, which the agent cannot infer from the schema. It does not explain why idempotentHint is false for a read call, but that is a minor omission.

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?

Front-loaded with the core purpose, then clearly delimited USE WHEN / NOT FOR / PARAMETERS / RETURNS blocks. Every line carries distinct information with no filler.

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, selection criteria, the batch limit, and the missing-page behavior, and an output schema exists to carry return shape. An agent has everything needed to decide and invoke correctly; the RETURNS line is a helpful summary rather than a redundancy.

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%, so titles and rationale are already documented; the description only echoes the 'max 50' constraint on titles and says nothing about the rationale audit parameter. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (get), resource (metadata/pages info), and scope (MULTIPLE pages in a single API call), which immediately distinguishes it from the singular sibling. The parenthetical field list (last edit, size, categories) pins down exactly what 'metadata' means.

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?

Explicit USE WHEN ('info for 2+ pages without their content') and NOT FOR clauses, each naming the correct alternative (mediawiki_get_page_info for single pages, mediawiki_batch_get_pages for content). This is textbook routing guidance.

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