Skip to main content
Glama
Vault Cortex Obsidian MCP Server

Vault Cortex Obsidian MCP Server

Get Outgoing Links

vault_get_outgoing_links
Read-onlyIdempotent

Lists every note, file, embed, and wikilink a note or canvas links to, helping audit broken links, check dependencies before editing, or navigate the vault graph forward.

Instructions

Find all notes and files a given note or canvas links to. For notes: [[wikilinks]], markdown, ![[embeds]], and wikilinks inside properties (e.g. related:). For canvas files: file nodes, not links inside text cards. Links inside code blocks are ignored; self-links are included. Each target is listed once, however often the note links to it.

Example: vault_get_outgoing_links({ path: "Projects/vault-cortex.md" }) Example: vault_get_outgoing_links({ path: "Diagrams/architecture.canvas" })

When to use: Navigating the graph forward, auditing broken links in one note or canvas, or checking dependencies before editing. For incoming links (what links TO a note), use vault_get_backlinks.

Behavior: Results can lag a file change by a few seconds.

Returns: JSON with path, outgoing_links (array of { path, title, exists, kind, bytes, daily_note_forward_ref } sorted by target path), and count. A target's path is the vault-relative path the link resolved to; a broken link's path is its target text without any #heading or |alias, with a markdown link's %-escapes decoded. When exists is true, kind "note" is a markdown note readable via vault_read_note and kind "file" a non-markdown file (.canvas, image, PDF) readable via vault_read_file; when exists is false the link is broken and kind is "note" even for a path like "diagram.png". title is null for files and broken links. daily_note_forward_ref is true on a broken link into the daily notes folder (a daily note not yet created, not breakage) and false otherwise, including when Obsidian's Daily Notes folder setting is the vault root or blank. bytes is the on-disk size (null for broken links), not the delivery cost: vault_read_file downscales a large image to fit response limits.

Errors:

  • "path must end in …" — add the .md or .canvas extension

  • A path that does not exist, or one in a dot-prefixed folder, returns an empty result (count 0), not an error, just as a note with no outbound links does; a note or canvas created or moved in the last few seconds may not appear yet. If you expected links, find valid paths with vault_search, vault_list_notes, or vault_list_files.

  • "[SqliteError]: …" — the index failed, not the call; the message says what to do

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": "vault_get_outgoing_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesExact vault-relative path including .md or .canvas extension (e.g. "Projects/vault-cortex.md"). Case-sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.54.16
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv0.36.0
    • changedInput schema / properties / path / description
      Previous value: -"Exact vault-relative path including .md extension (e.g. \"Projects/vault-cortex.md\"). Case-sensitive."New value: +"Exact vault-relative path including .md or .canvas extension (e.g. \"Projects/vault-cortex.md\"). Case-sensitive."
  3. Addedv0.32.1
  4. Removedv0.32.0
  5. Changed1 schema field changedv0.23.5
    • changedInput schema / properties / path / description
      Previous value: -"Vault-relative path to the note"New value: +"Exact vault-relative path including .md extension (e.g. \"Projects/vault-cortex.md\"). Case-sensitive."
  6. Added

TDQS

A4.6/5.0
Behavior4/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 real behavior beyond that: code-block links ignored, self-links included, one entry per target, index lag of a few seconds, and empty-result-rather-than-error semantics for missing or dot-prefixed paths. The error section adds diagnostic guidance. Slightly short of 5 only because the empty-result rule is buried in Errors rather than stated as primary behavior.

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 front-loaded and clearly sectioned (purpose, examples, when-to-use, behavior, returns, errors). The Returns paragraph is dense and long, but since no output schema exists that detail is largely load-bearing rather than padding.

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?

With no output schema, the description carries the full return contract and does so precisely: field-by-field semantics of path, title, exists, kind, bytes, daily_note_forward_ref, plus sorting and dedupe. It also tells the agent which sibling reader to use for each returned kind, which is exactly the follow-up an agent needs.

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 coverage is 100%, so the baseline is 3; the description still adds value by tying the parameter to failure modes ("path must end in … — add the .md or .canvas extension") and by showing two worked example invocations covering both .md and .canvas. It does not restate case-sensitivity, which the schema already covers.

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?

Opens with a specific verb+resource: "Find all notes and files a given note or canvas links to," then enumerates exactly what counts as a link for notes (wikilinks, markdown links, embeds, property wikilinks) versus canvas files. It explicitly distinguishes itself from vault_get_backlinks, so an agent can route without opening either 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?

Provides an explicit "When to use" list (forward graph navigation, broken-link auditing in one note, dependency checks before editing) and names the complementary tool for the inverse operation. The when-not case (incoming links) is stated with the exact alternative to call.

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