Skip to main content
Glama
aliasunder

Vault Cortex Obsidian MCP Server

by aliasunder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Notes

vault_list_notes
Read-onlyIdempotent

List Markdown note paths in an Obsidian vault, optionally filtered by folder or glob pattern. Returns vault-relative paths only, not note content.

Instructions

List .md file paths in the vault, optionally filtered by folder and/or glob pattern. Returns paths only — not content or metadata.

Example: vault_list_notes({ folder: "Projects" }) Example: vault_list_notes({ glob: "**/session-log.md" }) Example: vault_list_notes({ folder: "Projects", glob: "*.md" }) — the folder's top-level notes only

When to use: Browsing what exists in a folder by filename, or finding notes matching a path pattern. Prefer vault_search_by_folder when you need metadata (tags, type, related) along with paths. Prefer vault_search for content-based discovery. Use vault_read_note to read a note from the results.

Parameters:

  • folder names a whole folder and includes its subfolders: "Projects" covers "Projects/Archive" but not "ProjectsOld/". This tool reads the filesystem rather than the search index, so use the folder's exact letter case, as other results show it; on a case-sensitive filesystem a different case finds nothing.

  • glob matches each note's path inside folder (its vault-relative path when folder is omitted), case-sensitively. * stays within one folder level and ** spans any depth: with folder "Projects", ".md" lists the folder's top-level notes and "**/.md" every note under it. Returned paths are always vault-relative.

Behavior: Paths come back sorted by vault-relative path, uppercase before lowercase. Hidden (dot-prefixed) notes and folders are never listed, matching Obsidian; symlinked notes are included.

Errors:

  • A nonexistent folder or no glob matches returns an empty array, not an error.

  • "absolute path blocked" / "path traversal blocked" / "hidden path blocked" — the folder starts at the filesystem root, escapes the vault or names the vault root itself (e.g. "."), or is hidden like ".obsidian"; use a vault-relative folder outside hidden folders, and omit folder to list the whole vault.

Returns: JSON array of vault-relative path strings (e.g. ["Notes/idea.md", "Projects/plan.md"]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
globNoGlob pattern for note paths (e.g. "**/*session-log*.md").
folderNoVault-relative folder to list (e.g. "About Me", "Projects").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.54.7
    • changedInput schema / properties / folder / description
      Previous value: -"Folder path prefix (e.g. \"About Me\", \"Projects\"). Includes all subfolders."New value: +"Vault-relative folder to list (e.g. \"About Me\", \"Projects\")."
    • addedInput schema / properties / folder / minLength
      Added value: +1
    • changedInput schema / properties / glob / description
      Previous value: -"Glob pattern for path filtering (e.g. \"**/*session-log*.md\"). Supports * and ** wildcards. Combined with folder when both are set."New value: +"Glob pattern for note paths (e.g. \"**/*session-log*.md\")."
    • addedInput schema / properties / glob / minLength
      Added value: +1
  2. Addedv0.32.1
  3. Removedv0.32.0
  4. Changed2 schema fields changedv0.23.5
    • changedInput schema / properties / folder / description
      Previous value: -"Folder to list (e.g. \"About Me\", \"Projects\")"New value: +"Folder path prefix (e.g. \"About Me\", \"Projects\"). Includes all subfolders."
    • changedInput schema / properties / glob / description
      Previous value: -"Glob pattern to filter paths (e.g. \"Projects/**/*.md\", \"*.md\"). Supports * and ** wildcards."New value: +"Glob pattern for path filtering (e.g. \"**/*session-log*.md\"). Supports * and ** wildcards. Combined with folder when both are set."
  5. Added

TDQS

A5/5.0
Behavior5/5

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

Goes well past the annotations (readOnly/idempotent/non-destructive), disclosing sort order (uppercase before lowercase), hidden dot-file exclusion matching Obsidian, symlink inclusion, filesystem-vs-index sourcing, case sensitivity, and exact error semantics (empty array vs 'absolute path blocked'/'path traversal blocked'/'hidden path blocked'). This is rich context an agent cannot derive from any structured field.

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?

Long but tightly organized with headers (When to use / Parameters / Behavior / Errors / Returns), examples front-loaded after the first sentence, and no filler. Each section earns its space by covering a distinct decision an agent has to make.

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?

For a 2-param, no-output-schema read tool, the definition covers purpose, routing, parameter edge cases, ordering, hidden/symlink handling, and the full error taxonomy including remediation. Nothing needed to call it correctly is missing.

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?

Even though schema coverage is 100%, the description adds real meaning: folder includes subfolders but 'Projects' does not match 'ProjectsOld/', exact letter case is required on case-sensitive filesystems, and glob semantics are spelled out ('* stays within one level, ** spans any depth', matched against the vault-relative path, case-sensitive). Far exceeds the terse schema descriptions.

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 precise verb+resource+scope ('List .md file paths in the vault, optionally filtered by folder and/or glob pattern') and immediately bounds the output ('paths only — not content or metadata'). This distinguishes it cleanly from vault_search, vault_search_by_folder and vault_read_note.

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?

Explicit 'When to use' line plus two explicit routing rules: 'Prefer vault_search_by_folder when you need metadata... Prefer vault_search for content-based discovery. Use vault_read_note to read a note from the results.' Names both alternatives and the condition that selects each.

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

Deploy Server

Other Tools