markdown-vault-mcp

Backlinks

get_backlinks

Read-onlyIdempotent

List notes that link to a specified Markdown note, optionally limiting results, to trace references and understand how a note is used across the vault.

Instructions

List the notes that link to a note.

Use get_context when you also need its outlinks or similar notes.

Input Schema

Name	Required	Description
`path`	Yes	Path of the note linked to, such as `"notes/topic.md"`; case-sensitive.
`limit`	No	Maximum backlinks to return; omit for all.
`wait_for_pending_writes`	No	Wait for recent index writes. On timeout, answer from the current index with _meta.index_stale=true. Default false.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv6.1.0Nov 2, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of backlinks to return. Omitted (the\ndefault) returns all."New value: +"Maximum backlinks to return; omit for all."

changedInput schema / properties / path / description

Previous value: -"Relative path of the target document (e.g.\n\"notes/topic.md\"). Case-sensitive."New value: +"Path of the note linked to, such as `\"notes/topic.md\"`; case-sensitive."

Changed1 schema field changedv5.0.0Sep 15, 2026

changedInput schema / properties / wait_for_pending_writes / description

Previous value: -"When True, wait until your recent\ndocument mutations have been applied to the\nindex before answering, so the results reflect those changes.\nUse it right after modifying notes when this read must see\nthem (e.g. right after a document mutation whose\neffect this read should reflect). Default\nFalse answers immediately from the current index — almost\nalways already up to date; inspect the response's\n``_meta.index_stale`` field to tell whether a write was still\nin flight. Bounded by a server timeout (default 60s); on\ntimeout it answers from the current index rather than waiting\nlonger."New value: +"Wait for recent index writes. On timeout, answer from the current index with _meta.index_stale=true. Default false."

Changed1 schema field changedv4.0.0Aug 26, 2026

changedInput schema / properties / wait_for_pending_writes / description

Previous value: -"When True, wait until your recent\nwrite/edit/delete/rename operations have been applied to the\nindex before answering, so the results reflect those changes.\nUse it right after modifying notes when this read must see\nthem (e.g. right after a write/edit/delete/rename whose\neffect this read should reflect). Default\nFalse answers immediately from the current index — almost\nalways already up to date; inspect the response's\n``_meta.index_stale`` field to tell whether a write was still\nin flight. Bounded by a server timeout (default 60s); on\ntimeout it answers from the current index rather than waiting\nlonger."New value: +"When True, wait until your recent\ndocument mutations have been applied to the\nindex before answering, so the results reflect those changes.\nUse it right after modifying notes when this read must see\nthem (e.g. right after a document mutation whose\neffect this read should reflect). Default\nFalse answers immediately from the current index — almost\nalways already up to date; inspect the response's\n``_meta.index_stale`` field to tell whether a write was still\nin flight. Bounded by a server timeout (default 60s); on\ntimeout it answers from the current index rather than waiting\nlonger."

First observedv3.1.0Jul 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare the tool read-only, idempotent and non-destructive. The description adds no behavioral context of its own, such as ordering, whether embedded links or aliases count, or index dependence. The stale-index behavior is documented only in the schema.

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 with no waste. The purpose comes first and the routing guidance follows.

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?

This is a simple read-only tool with an output schema, full parameter docs and rich annotations, so the brief description is mostly sufficient. Some notes on index-based behavior or link-type coverage would complete it.

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 coverage is 100%, and the schema documents case-sensitivity, the 'omit for all' default and timeout staleness. The description adds nothing about the parameters, so the baseline score 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?

"List the notes that link to a note" gives a specific verb and resource, and it defines inbound links precisely. That separates it from get_outlinks and get_most_linked, and the description also names get_context explicitly.

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?

It names get_context as the alternative and gives the condition for choosing it: when outlinks or similar notes are also needed. It does not mention vault_graph_neighborhood or get_connection_path, which overlap in a large sibling set.

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