Skip to main content
Glama
bezata

kObsidian MCP

List Notes And Folders

notes.list
Read-onlyIdempotent

List notes or folders in your Obsidian vault, scoped by folder and filtered by creation or modification date. Recursively includes subfolders. Read-only.

Instructions

List notes and/or folders in the vault, optionally scoped to a folder and filtered by creation/modification date. include selects what to return (notes, folders, or both). recursive:true descends into subfolders. since/until (ISO dates) combined with dateField (created or modified, default modified) narrow the result by date. Read-only.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoOptional folder to scope the listing.
includeNoWhat to list — markdown notes, folders, or both (returns items tagged by kind).notes
recursiveNoRecurse into subfolders. Default false.
sinceNoOnly include items dated on or after this ISO date.
untilNoOnly include items dated on or before this ISO date.
dateFieldNoWhich date the `since`/`until` filter applies to. Defaults to `modified`.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesNumber of items in `items`.
itemsYesList of result items; per-item shape depends on the tool.
Behavior5/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true. Description adds: 'Read-only', vaultPath override behavior, date filtering defaults, and recursion behavior. 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?

Two well-structured sentences, front-loaded with main action. Covers all important aspects without unnecessary details.

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 7 parameters, most self-explanatory, and an output schema exists, the description covers scoping, filtering, recursion, vault selection, and read-only nature. Complete for a list tool.

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 86% (high). Description adds meaning beyond schema: explains include options, dateField defaults, recursive default false, vaultPath override. Adds value over 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?

Description clearly states the tool lists notes and/or folders in the vault, with scoping options. It distinguishes from siblings like notes.search (search) and notes.read (single note).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains scoping, filtering, and recursion. Mentions read-only and vault selection. However, does not explicitly state when to use this tool vs alternatives like notes.search.

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/bezata/kObsidian'

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