kObsidian MCP

Get Backlinks

links.backlinks

Read-onlyIdempotent

Find every note that links to a target note, supporting wiki-style and markdown links. Optionally include context snippets to judge link intent without reopening sources.

Instructions

Find every note that links TO a target note (inbound references). Supports both wiki-style [[Note]] and markdown-style [text](Note.md) links. When includeContext:true, each result carries a contextLength-char snippet of surrounding text so the agent can judge link intent without re-reading each source. Read-only. For outbound links (what a note points AT), use links.outgoing.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Vault-relative path of the note whose inbound links we want.
`vaultPath`	No
`contextLength`	No	Characters of context per hit. Default 80.
`includeContext`	No	When true, each result carries a snippet of surrounding text for each backlink.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	List of result items; per-item shape depends on the tool.
`total`	Yes	Number of items in `items`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.5Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed8 schema fields changedv0.1.2Apr 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / contextLength / description

Added value: +"Characters of context per hit. Default 80."

addedInput schema / properties / includeContext / description

Added value: +"When true, each result carries a snippet of surrounding text for each backlink."

addedInput schema / properties / path / description

Added value: +"Vault-relative path of the note whose inbound links we want."

addedOutput schema / description

Added value: +"Standard list envelope used by list/search tools."

addedOutput schema / properties / items / description

Added value: +"List of result items; per-item shape depends on the tool."

addedOutput schema / properties / items / items / description

Added value: +"Freeform object. The specific shape depends on the tool; see the tool description."

addedOutput schema / properties / total / description
```
Added value: +"Number of items in `items`."
```

First observedv0.1.0Apr 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds meaningful behavioral context: it supports both wiki-style and markdown-style links, describes the includeContext/contextLength snippet behavior, and explains vault resolution precedence. No contradiction with annotations.

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 tight paragraphs with the core purpose front-loaded. Each sentence adds useful routing or behavioral information; only 'Read-only.' slightly duplicates the annotation, but it is brief and does not hurt clarity.

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?

Given the output schema exists and annotations cover safety, the description covers purpose, alternatives, vault behavior, and parameter semantics. An agent has everything needed to decide when to use this tool and how to invoke it correctly.

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

Parameters4/5

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

Schema covers path, contextLength, and includeContext, while the description adds the missing meaning of vaultPath ('explicit vaultPath argument ... always wins') and clarifies how includeContext and contextLength interact. This goes beyond the schema, though a touch more detail on contextLength's default could strengthen it.

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: 'Find every note that links TO a target note (inbound references).' It clearly differentiates from the links.outgoing sibling, so an agent can identify the tool's purpose without opening the schema.

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?

Explicitly names the alternative for outbound links ('use links.outgoing') and explains when an explicit vaultPath wins over the active vault. It also points to vault.current and vault.select for vault selection, making usage conditions concrete.

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

Deploy Server