Skip to main content
Glama

get-links-here

Read-onlyIdempotent

List wiki pages that reference a target page via wikilinks, transclusions, or file usage. Filter results by namespace or redirect status.

Instructions

Lists pages that reference a target wiki page, returning each referencing page's title, page ID, namespace ID, and whether it is a redirect. The type parameter selects the relationship — wikilinks (pages that link to the target), transclusions (pages that embed it, such as a template), or fileusage (pages that display it, for File pages) — one relationship per call. With expandRedirects, a referencing redirect also yields the pages that link through it (wikilinks and fileusage only), each tagged with the via redirect. Filter by namespace ID or by redirect status. For members of a category, use get-category-members; for full-text content search, use search-page. Returns up to 500 per call; paginate with continueFrom.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesWiki page title to find references to (the link target). A File title when type is fileusage.
typeNoInbound relationship to list: wikilinks (pages that link to the target), transclusions (pages that embed it), or fileusage (pages that display it)wikilinks
namespacesNoNamespace IDs to filter the referencing pages by
filterNoFilter the referencing pages by redirect statusall
expandRedirectsNoWhen a referencing page is a redirect to the target, also return the pages that link through it. Applies to wikilinks and fileusage only.
limitNoMaximum referencing pages to return (1..500)
continueFromNoOpaque continuation token from the previous response; omit on first call
wikiNoWiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.
Behavior4/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true, which the description does not contradict. The description adds behavioral details like the 500-per-call limit, expandRedirects behavior, and tagging 'via redirect', providing useful context beyond the annotations.

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?

The description is moderately lengthy but well-structured: it starts with the main purpose, then details parameters and special behavior. Every sentence serves a purpose, though a slight trim could improve brevity without losing key info.

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?

With 8 parameters and no output schema, the description covers the tool's functionality thoroughly, including return fields and pagination. It could mention that the output includes a continuation token, but otherwise it is complete for effective usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage, and the description adds significant meaning to each parameter. For example, it explains the 'type' parameter as selecting relationship, 'expandRedirects' applies to wikilinks and fileusage, and 'continueFrom' for pagination. The description enriches the schema with practical usage details.

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 the tool's purpose: listing pages that reference a target wiki page, with specific details about the returned fields and relationship types. It explicitly distinguishes from siblings like get-category-members and search-page, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear usage context: one relationship per call, pagination with continueFrom, and mentions alternative tools for category membership and full-text search. It lacks explicit 'when not to use' statements but gives sufficient guidance to select the appropriate tool.

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/ProfessionalWiki/MediaWiki-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server