Skip to main content
Glama

Get Backlinks

vault_get_backlinks
Read-onlyIdempotent

Find all notes that link to a specific note via wikilinks or markdown links, revealing its context and importance in the knowledge graph. Backlinks include the note itself if it self-links.

Instructions

Find all notes that link to a given note via incoming [[wikilinks]] or markdown. Reveals what references the target — its context and importance in the knowledge graph, invisible without a graph query. Both link styles are captured; links inside code blocks are ignored, and a note that links to itself appears in its own backlinks.

Example: vault_get_backlinks({ path: "Projects/vault-cortex.md" })

When to use: Understanding what references a note or assessing its connectivity. For outgoing links (what a note links TO), use vault_get_outgoing_links. To find notes with no backlinks at all, use vault_find_orphans.

Parameters:

  • path must be the exact vault-relative path — case-sensitive, including the .md extension.

Errors:

  • A note with no inbound links, or a path not in the index, returns an empty array (count 0), not an error — don't use this as an existence check.

Returns: JSON with path (the queried note), backlinks (array of { path, title }, sorted by title), and count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesVault-relative path to the note (e.g. "Projects/vault-cortex.md")
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint false, idempotentHint. Description adds valuable details: captures both link styles, ignores code blocks, self-links included, empty array vs error. No contradiction.

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?

Well-structured with clear sections: purpose, example, usage guidance, parameter clarification, error behavior, return format. Slightly long but every sentence adds value; no wasted words.

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 single parameter, no output schema, and rich sibling context, description fully covers return format, edge cases (empty results), and provides a concrete example. Agent has sufficient information.

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

Parameters5/5

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

Schema has 100% coverage with description for path. The description adds critical constraints: exact vault-relative path, case-sensitive, .md extension required. Provides an example value.

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?

The description clearly states the tool finds all notes linking to a given note via [[wikilinks]] or [markdown](links), revealing context and importance. It distinctly differentiates from sibling tools like vault_get_outgoing_links and vault_find_orphans.

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?

Provides explicit when-to-use guidance ('Understanding what references a note or assessing its connectivity') and names specific alternatives (vault_get_outgoing_links for outgoing, vault_find_orphans for orphans).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aliasunder/vault-cortex'

If you have feedback or need assistance with the MCP directory API, please join our Discord server