Skip to main content
Glama

mediawiki_bulk_replace

Destructive

Update text across multiple MediaWiki pages simultaneously using find and replace. Preview changes before applying to ensure accuracy.

Instructions

Update text across MULTIPLE pages at once.

USE WHEN: User says "update everywhere", "fix on all pages", "change brand name across docs", "update in all documentation".

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

PARAMETERS:

  • find: Text to find (required)

  • replace: Replacement text (required)

  • pages: Array of specific pages (optional)

  • category: Update all pages in category (optional)

  • use_regex: Treat find as regex (default false)

  • preview: Preview changes (ALWAYS use true first!)

  • limit: Max pages to update (default 50)

  • summary: Edit summary

WARNING: Always use preview=true first to verify matches before applying.

RETURNS: Changes per page. Set preview=false to apply all changes. Includes revision ID, diff URL, and undo instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rationaleYesRequired one-sentence explanation of why you are making this change. Stored in the audit log for post-hoc intent reconstruction.
pagesNoPage titles to process
categoryNoCategory to get pages from (alternative to pages)
findYesText to find
replaceYesReplacement text
use_regexNoTreat 'find' as a Go RE2 regex. Characters like . [ ] * + ? ( ) have special meaning; escape with backslash for literal match. Max 500 chars.
previewNoPreview changes without saving
summaryNoEdit summary
limitNoMax pages to process (default 10, max 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pages_processedYes
pages_modifiedYes
total_changesYes
previewYes
resultsYes
messageYes
Behavior5/5

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

Annotations include destructiveHint and openWorldHint; the description adds critical warnings like 'Always use preview=true first' and explains the preview workflow, return details (revision ID, diff URL, undo instructions), adding value 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?

The description is well-structured with sections for use cases, parameters, and warnings. Every sentence is informative without unnecessary 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 9 parameters, complex workflows (preview, apply, regex, category), and an output schema, the description covers the critical workflow, warnings, differentiation from siblings, and return information thoroughly.

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 description coverage is 100%, so baseline is 3. The description adds extra meaning by emphasizing preview importance and clarifying parameter usage in context (e.g., pages vs category). It is well-organized but does not dramatically extend beyond the schema.

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 'Update text across MULTIPLE pages at once.' It uses a specific verb and resource, and distinguishes itself from the sibling tool mediawiki_find_replace for single-page changes.

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 states 'USE WHEN: User says update everywhere...' and 'NOT FOR: Single page changes (use mediawiki_find_replace - more efficient).' Provides clear context and an alternative.

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