Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

List Notes And Folders

notes.list
Read-onlyIdempotent

List notes and folders in an Obsidian vault, scoped by folder and filtered by creation or modification date. Supports recursion.

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.3.5
  2. Removedv0.3.4
  3. Changed12 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / dateField
      Added value: +{
+  "description": "Which date the `since`/`until` filter applies to. Defaults to `modified`.",
+  "enum": [
+    "created",
+    "modified"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / directory
      Removed value: -{
-  "maxLength": 255,
-  "minLength": 1,
-  "type": "string"
-}
    • addedInput schema / properties / folder
      Added value: +{
+  "description": "Optional folder to scope the listing.",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / include
      Added value: +{
+  "default": "notes",
+  "description": "What to list — markdown notes, folders, or both (returns items tagged by kind).",
+  "enum": [
+    "notes",
+    "folders",
+    "both"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / recursive / description
      Added value: +"Recurse into subfolders. Default false."
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only include items dated on or after this ISO date.",
+  "format": "date",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+  "type": "string"
+}
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Only include items dated on or before this ISO date.",
+  "format": "date",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+  "type": "string"
+}
    • addedOutput schema / description
      Added value: +"Standard list envelope used by list/search tools."
    • addedOutput schema / properties / items / description
      Added value: +"List of result items; per-item shape depends on the tool."
    • addedOutput schema / properties / items / items / description
      Added value: +"Freeform object. The specific shape depends on the tool; see the tool description."
    • addedOutput schema / properties / total / description
      Added value: +"Number of items in `items`."
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds valuable behavior not in annotations: parameter semantics (include, recursive, dateField interplay), the default modified date, and the vault scoping override. It does not contradict annotations and reinforces the read-only nature. It stops short of describing the exact output structure (e.g., which fields are returned per item), but the output schema covers that. With annotations covering safety, the description adds meaningful context, earning a 4.

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 two succinct paragraphs. The first states the action and key parameters; the second addresses vault scoping. Every sentence contributes new information—no filler or redundancy. It is front-loaded with the core purpose and parameter semantics, making it easy to scan. This is appropriately sized for a tool with 7 parameters and no required args.

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 the tool's complexity (7 params, 0 required) and the presence of an output schema, the description covers all essential aspects: purpose, parameter behavior, default values, recursion, and the vault selection precedence. It also references sibling tools (vault.current, vault.select) for context. Nothing critical is missing for an agent to call it correctly. The read-only nature is reinforced, and the output format is left to the schema. This is complete.

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 description coverage is 86%, so most parameters already have meaning in the schema. The description adds relational value beyond that: it ties since/until to dateField, explains recursive behavior, clarifies include options as notes, folders, or both (tagged by kind), and spells out the vaultPath precedence. This goes beyond individual parameter descriptions, helping an agent understand how parameters combine. Since coverage is high, the baseline is 3, but the description elevates it to 4.

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 opens with a specific verb (list) and resource (notes/folders), and clarifies optional scoping and filtering. It distinguishes itself from siblings like notes.read (read a single note), notes.search (search), and vault.list (list vaults) by clearly stating what it enumerates in the session-active vault. The purpose is unambiguous and easy to differentiate at a glance.

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?

The description gives clear context: list notes/folders, optionally scoped to a folder and date range. It mentions read-only behavior and explains vault selection precedence (vaultPath wins), which is critical for correct invocation. It does not explicitly name alternatives for when not to use it (e.g., 'for full-text search use notes.search'), but the scope is self-evident and enough for an agent to decide appropriately. A small deduction for not enumerating exclusions.

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