Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_external_links_batch

Read-only

Retrieve external URLs from up to 10 MediaWiki pages at once, grouped by source page, to collect links for multi-article analysis.

Instructions

Batch retrieve external URLs from multiple pages at once.

USE WHEN: User asks "get links from these 5 pages", "collect URLs from multiple articles".

NOT FOR: Single page (use mediawiki_get_external_links - more efficient).

PARAMETERS:

  • titles: Array of page names (required, max 10)

RETURNS: External URLs grouped by source page.

Input Schema

NameRequiredDescriptionDefault
titlesYesPage titles to get external links from (max 10)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

NameRequiredDescriptionDefault
pagesYes
total_linksYes

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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=true, idempotentHint=false), lowering the bar. The description adds useful framing: it explains the batch efficiency trade-off and that results are grouped by source page, which matters for interpreting a multi-page read. It does not explain the idempotentHint=false nuance, so it is strong but not complete.

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 a single summary line, then clearly labeled USE WHEN / NOT FOR / PARAMETERS / RETURNS sections. Each sentence earns its place, with only trivial repetition of the max-10 constraint already in the schema.

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?

For a bounded batch-read tool, the definition covers purpose, routing, the key constraint (max 10), and return grouping. With an output schema present and annotations covering safety, nothing an agent needs to invoke this correctly is missing.

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 both parameters are already documented, and the description only restates titles (required, max 10) without adding syntax or format guidance. Baseline 3 is correct when the schema does the heavy lifting; the description adds no meaning beyond it.

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 and resource ("Batch retrieve external URLs from multiple pages") with explicit scope (multiple pages at once). It immediately distinguishes itself from the single-page sibling mediawiki_get_external_links, so an agent can route without opening either schema.

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?

Provides explicit USE WHEN triggers ("get links from these 5 pages") and an explicit NOT FOR exclusion that names the alternative tool for the single-page case. Nothing about when to pick this vs. the sibling is left to inference.

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