Skip to main content
Glama
ttpears

mediawiki-mcp

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-page-links

Retrieve outgoing links from a MediaWiki page or find backlinks to it, returning link titles and namespaces.

Instructions

Get outgoing links from a page (direction="from") or find all pages that link to it (direction="to", i.e. backlinks). Returns link titles and namespaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wikiNoWiki name (uses default if omitted)
limitNoMaximum number of links
titleYesPage title
directionNoLink direction: "from" for outgoing links, "to" for backlinksfrom
continue_fromNoContinuation token for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.3.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (link titles and namespaces) and direction semantics, but says nothing about read-only nature, permissions, rate limits, or pagination behavior despite a continue_from param existing. Some context, but incomplete for a query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no waste, front-loading the two-mode behavior and return format. Efficient, though it could be more concise about the namespace detail.

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

Completeness3/5

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

With no annotations and no output schema, the description does enough to orient an agent on the core query and return shape, but omits pagination semantics (continue_from) and safety profile. Adequate but with clear gaps for a 5-param, no-annotation tool.

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 the schema already documents all five parameters including the direction enum. The description restates the direction semantics already in the schema but adds no new syntax, format, or constraint details. Baseline 3 applies.

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) and resource (page links), and explicitly distinguishes the two modes via direction=from vs direction=to. No sibling tool covers page links, so the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains what each direction value means, which is implied usage guidance, but offers no when-to-use vs alternatives, no prerequisites, and no routing to other tools.

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