Skip to main content
Glama

mediawiki_find_broken_internal_links

Read-onlyIdempotent

Scans wiki pages for broken internal [[links]] and reports source page, line number, and context to help fix dead links.

Instructions

Find internal wiki [[links]] pointing to non-existent pages.

USE WHEN: User asks "find broken wiki links", "check for dead internal links", "find [[links]] to missing pages".

NOT FOR: Checking external HTTP URLs (use mediawiki_check_links).

PARAMETERS:

  • pages: Array of pages to scan (optional)

  • category: Scan all pages in category (optional)

  • limit: Max pages to scan (default 20)

RETURNS: Broken links with source page, line number, and context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
pagesNoPage titles to check for broken internal links
categoryNoCategory to get pages from (alternative to pages)
limitNoMax pages to check (default 20, max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pages_checkedYes
broken_countYes
pagesYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. Description adds scanning behavior (pages/category/limit) and return details (broken links with source, line, context), which is useful but does not significantly extend 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?

Description is well-structured with clear sections (purpose, usage, parameters, returns), concise without waste. Front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given annotations and output schema, the description covers purpose, usage, parameters, and returns adequately. Minor gaps: edge cases (e.g., both pages and category specified) not addressed, but overall complete.

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 baseline is 3. Description adds moderate value by rephrasing parameter purpose and default values, but misses the max 100 constraint mentioned in schema. Does not significantly improve understanding beyond 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?

Description clearly states it finds internal wiki links pointing to non-existent pages, using specific verb+resource. Distinguishes from sibling tools like mediawiki_check_links by focusing on internal dead links.

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' and 'NOT FOR' sections, and names the alternative tool for external URLs. This gives the agent clear guidance on when to invoke 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