Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

liquipedia_links

Read-only

Lists outgoing links from source-selected pages on one Liquipedia wiki with namespace, title, redirect, limit, and continuation filters. Use wiki slugs from liquipedia_wikis and namespace IDs from liquipedia_enums; preserve Liquipedia attribution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wiki": "<wiki>"
    },
    "name": "liquipedia_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
wikiYesRequired Liquipedia wiki slug from liquipedia_wikis.
pldirNoOptional source ordering direction.
revidsNoSource revision IDs; provide exactly one selector type. Up to 50 page selectors are supported by MediaWiki.
titlesNoSource page titles; provide exactly one selector type. Up to 50 page selectors are supported by MediaWiki.
pageidsNoSource page IDs; provide exactly one selector type. Up to 50 page selectors are supported by MediaWiki.
pllimitNoPage size from 1 through 500, or the string max; source default is 10.
continueNoOptional global MediaWiki continuation value.
pltitlesNoOptional source title filter, with up to 50 target titles.
redirectsNoResolve redirects for the selected source page(s).
plcontinueNoOptional native links continuation value.
plnamespaceNoRepeatable linked-page namespace IDs as numbers, or the string * for all namespaces.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds a genuine non-obvious obligation ('preserve Liquipedia attribution') and the single-wiki scoping constraint, but says nothing about pagination behavior or result characteristics beyond what the continuation parameters imply.

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 sentences with the core operation front-loaded and the dependency/attribution notes trailing. No filler, though the second sentence packs three unrelated obligations into one clause chain.

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?

For an 11-parameter tool with full schema coverage and an output schema, the description supplies the essentials: what is listed, what selects the source, what filters apply, and where to source valid values. Nothing critical is missing, though it never clarifies the exactly-one-selector rule that the schema encodes.

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 the schema already explains every parameter including the selector exclusivity and limits; the description merely echoes the filter categories (namespace, title, redirect, limit, continuation). Its pointer to liquipedia_enums for namespace IDs duplicates what the schema's own descriptions already state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists outgoing links from source-selected pages on one Liquipedia wiki') and enumerates the filter dimensions, so the operation is immediately identifiable. It does not explicitly name the contrasting sibling (liquipedia_backlinks), so the inbound/outbound distinction must be inferred from the word 'outgoing'.

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?

Provides real usage context by routing parameter values to liquipedia_wikis (wiki slugs) and liquipedia_enums (namespace IDs), and flags the attribution obligation. However, it gives no guidance on when to prefer this over alternatives such as liquipedia_backlinks or liquipedia_page, leaving selection to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources