Skip to main content
Glama

List backlinks

list_backlinks
Read-only

Return the set of notes that wikilink to the given slug. Useful for discovering related content and upstream references.

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": {
      "slug": "<slug>"
    },
    "name": "list_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTarget note slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds only that the result is a 'set of notes', leaving open whether backlinks are direct-only or transitive, how results are ordered, and whether any limit applies — meaningful gaps for a graph-traversal query.

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?

Two short sentences with zero filler; the core definition is front-loaded and the secondary use-case follows. Nothing could be removed without losing information.

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 a single-parameter read-only lookup with full schema coverage and rich annotations, the description covers what the tool returns and why to call it. Only the depth/ordering semantics of the backlink result are left unstated, a minor gap given the tool's simplicity.

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% and the single parameter is documented as 'Target note slug'. The description's phrase 'the given slug' adds no format, resolution, or aliasing detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and resource — 'Return the set of notes that wikilink to the given slug' — which unambiguously defines backlinks as inbound wikilinks. It is clearly distinct from siblings like list_by_tag or search_collection, but it never explicitly contrasts with them, so it falls short of a 5.

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?

'Useful for discovering related content and upstream references' implies a usage context but gives no when-not guidance and names no alternative tool for exploring links in the other direction. The agent must infer that this is the tool for inbound references rather than being told.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources