Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_backlinks

Read-only

Find pages linking to a specific wiki page. Use it to answer 'what links here' and identify incoming references, with optional namespace, limit, and redirect filtering.

Instructions

Get pages that link TO a specific page ("What links here").

USE WHEN: User asks "what links to X", "which pages reference the API", "show incoming links".

NOT FOR: Outgoing external links (use mediawiki_get_external_links).

PARAMETERS:

  • title: Page name (required)

  • namespace: Filter by namespace (optional)

  • limit: Max backlinks (default 50)

  • include_redirects: Include redirect pages (default false)

RETURNS: List of pages that link to the target page.

Input Schema

NameRequiredDescriptionDefault
limitNoMax backlinks to return (default 50, max 500)
titleYesPage title to find backlinks for
namespaceNoFilter by namespace (-1 for all, 0 for main)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
include_redirectsNoInclude redirect pages in results

Output Schema

NameRequiredDescriptionDefault
countYes
titleYes
has_moreYes
backlinksYes

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint=false, so safety is covered. The description adds useful behavioral context: the directionality of the result set, the default limit of 50, and that redirects are excluded by default, which help an agent predict output scope without opening the schema.

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?

Front-loaded with the core purpose, then cleanly sectioned into USE WHEN / NOT FOR / PARAMETERS / RETURNS. Slightly redundant in re-listing parameters and return values that the schema and output schema already carry, but the structure is efficient and scannable.

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?

With annotations covering the safety profile and an output schema covering return shape, the description supplies everything else an agent needs: purpose, direction, triggers, exclusions, and defaults. Nothing required to invoke it 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 description coverage is 100%, so all five parameters (including rationale) are already documented in the schema. The description's parameter list largely restates the schema's names, required flags, and defaults, adding no format details or semantic nuance beyond it; baseline 3 is appropriate.

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 ('Get pages that link TO a specific page') and disambiguates direction with the canonical 'What links here' phrasing. It also names the distinguishing sibling concept (incoming vs outgoing links), so an agent can tell it apart from mediawiki_get_external_links immediately.

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 with concrete user phrasings ('what links to X', 'which pages reference the API') and a NOT FOR clause that routes the agent to mediawiki_get_external_links for the opposite direction. Both when-to-use and when-not-to-use are covered.

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