Skip to main content
Glama

Get Outgoing Links

vault_get_outgoing_links
Read-onlyIdempotent

Retrieve all outgoing links from a note, including wikilinks and markdown links. Each link shows whether the target exists, helping identify broken links.

Instructions

Find all notes a given note links to via outgoing [[wikilinks]] or markdown. Each entry has an exists flag — false marks a broken link (target not in the vault). Both link styles are captured; links inside code blocks are ignored, and a note that links to itself appears in its own outgoing links.

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

When to use: Seeing what a note references, navigating the graph forward, or finding broken links in one note. For incoming links (what links TO a note), use vault_get_backlinks.

Parameters:

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

Errors:

  • A note with no outbound links, or a path not in the index, returns an empty array (count 0), not an error.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesVault-relative path to the note
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds context such as ignoring links in code blocks, including self-links, and returning empty array for no links or missing paths, with no contradictions.

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?

The description is well-structured with front-loaded key information, example usage, when-to-use guidance, parameter details, error behavior, and return format, all without unnecessary content.

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?

Despite no output schema, the description fully details the return JSON structure and error handling, making it complete for the tool's moderate complexity.

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?

The description adds critical detail beyond the schema's description, specifying that the path must be exact, case-sensitive, and include the .md extension, and provides an example.

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 it finds all notes a given note links to via wikilinks or markdown links, specifies the exists flag for broken links, and distinguishes itself from the sibling tool vault_get_backlinks.

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?

The description explicitly states when to use the tool (e.g., seeing what a note references, navigating the graph forward, finding broken links) and directs users to vault_get_backlinks for incoming links.

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