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, filtered by folder or glob pattern. Browse filenames before reading content, or find notes matching a path pattern.

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; without a glob, notes in its subfolders are listed too: "Projects" covers "Projects/Archive" but not "ProjectsOld/". 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 every note under it.

Behavior: Paths come back sorted by vault-relative path in code-unit order (uppercase before lowercase). Hidden (dot-prefixed) notes and folders are never listed; 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" — use a vault-relative folder outside hidden folders, or omit folder to list the whole vault.

  • "ENAMETOOLONG: …", "EACCES: …" or another filesystem error code — the message names the folder it could not read, and what to do; until then, pass a folder outside it.

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

Input 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. Changed1 schema field changedv0.54.16
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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
  3. Addedv0.32.1
  4. Removedv0.32.0
  5. 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."
  6. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds sort order, hidden-file exclusion, symlink inclusion, empty-array-not-error semantics, and the exact error strings an agent may encounter plus recovery guidance. None of that is derivable from the annotations.

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?

Front-loaded with the core contract, then examples, routing guidance, parameter notes, behavior, errors, and returns in a scannable hierarchy. Length is driven by genuinely non-obvious semantics (case sensitivity, glob scoping, error strings), and the mild restatement of the return type is harmless.

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?

There is no output schema, but the 'Returns' line specifies the exact shape (JSON array of vault-relative path strings), and error conditions and their remediation are all covered. Nothing an agent needs to call this 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?

Schema coverage is 100%, so the baseline is 3, but the description substantially enriches it: folder recurses into subfolders unless a glob is given, exact letter case matters on case-sensitive filesystems, and glob is matched against the path inside folder with '*' vs '**' depth semantics spelled out.

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?

States a specific verb (list), resource (.md file paths in the vault), and explicit scope limits ('Returns paths only — not content or metadata'), which immediately separates it from content/metadata searching siblings.

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?

A dedicated 'When to use' line names the positive case (browsing by filename, matching path patterns) and explicitly routes to three alternatives: vault_search_by_folder for metadata, vault_search for content, vault_read_note for reading. That is when/when-not/alternatives in full.

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