obsidian-mcp

Get backlinks

get_backlinks

Read-only

List notes linking to a given Obsidian note to assess its references before editing or deleting, or to follow the knowledge graph backward.

Instructions

List notes that link TO a given note (wikilinks, embeds and relative markdown links). Use before editing or deleting to understand what references it, or to follow the knowledge graph backwards.

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": {
      "path": "<path>"
    },
    "name": "get_backlinks"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Vault-relative note path

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds useful behavioral detail about the link types included and the direction of links (incoming, not outgoing). This adds value beyond the structured data, though return format and pagination are not described.

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 sentences, front-loaded with the core action and scope, followed by practical usage contexts. No filler or redundant restatement of the name.

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?

For a simple one-parameter read tool with readOnlyHint, the description explains the result (list of backlink notes), the link types included, and when to use it. No critical information is missing for an agent to select and invoke it correctly.

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 covers the single required 'path' parameter with description 'Vault-relative note path', so schema coverage is 100%. The tool description adds no further parameter semantics beyond referring to a given note, so the 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 'List notes that link TO a given note' with explicit link types (wikilinks, embeds, relative markdown links). This clearly distinguishes the tool from siblings like list_notes and read_note by focusing on incoming references.

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?

Explicitly prescribes when to use it: 'before editing or deleting to understand what references it, or to follow the knowledge graph backwards.' It lacks when-not guidance or named alternatives, which would be needed for a 5.

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

Deploy Server