Skip to main content
Glama
aliasunder

Vault Cortex Obsidian MCP Server

Recent Notes

vault_recent_notes
Read-onlyIdempotent

List recently modified or created notes in an Obsidian vault, sorted by timestamp. Use it to catch up on changes, find recent work, or orient after a break.

Instructions

List recently modified or created notes, sorted by timestamp — a time-ordered window into the vault, not a date-range filter.

Example: vault_recent_notes({ sort_by: "modified", limit: 10 }) Example: vault_recent_notes({ sort_by: "created", limit: 5 })

When to use: Catching up on vault changes, finding recent work, or orienting after a break. Prefer vault_search for content-based discovery. Prefer vault_search_by_folder for browsing a specific folder.

Parameters:

  • sort_by + limit interact: "modified" (default) uses filesystem mtime, so every note has a value and limit works predictably. "created" uses the frontmatter created property — notes without it sort last (not excluded), so a small limit may return only notes that have the property; increase limit or use "modified" for broader coverage.

  • "modified" includes any file write (content edits, property changes, sync touches), so recently-synced notes appear recent even without user edits.

Errors:

  • An empty vault returns an empty array, not an error.

Returns: JSON array of note metadata (path, title, tags, related, folder, type, created, modified, bytes, leading_callout?, additional_properties), sorted descending by chosen timestamp. created is null when the property is missing; bytes is on-disk file size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, no upper cap)
sort_byNoSort order (default "modified")modified

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.50.0
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / sort_by / default
      Added value: +"modified"
  2. Addedv0.32.1
  3. Removedv0.32.0
  4. Changed2 schema fields changedv0.23.6
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20, no upper cap). Example: limit: 5 returns the top 5 by chosen timestamp."New value: +"Max results (default 20, no upper cap)"
    • changedInput schema / properties / sort_by / description
      Previous value: -"\"created\" or \"modified\" (default). \"modified\" uses filesystem mtime (any write, including sync, updates it). \"created\" uses the frontmatter created property — notes without it sort last; pair with a higher limit to include them."New value: +"Sort order (default \"modified\")"
  5. Changed2 schema fields changedv0.23.5
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default 20). When sorting by created, notes without a created property sort last and may fall outside a small limit."New value: +"Max results (default 20, no upper cap). Example: limit: 5 returns the top 5 by chosen timestamp."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property sort to the bottom of created-sorted results — with a small limit they may not appear at all."New value: +"\"created\" or \"modified\" (default). \"modified\" uses filesystem mtime (any write, including sync, updates it). \"created\" uses the frontmatter created property — notes without it sort last; pair with a higher limit to include them."
  6. Changed2 schema fields changedv0.23.3
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default 20)"New value: +"Max results to return (default 20). When sorting by created, notes without a created property sort last and may fall outside a small limit."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property are excluded from created-sorted results."New value: +"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property sort to the bottom of created-sorted results — with a small limit they may not appear at all."
  7. Changed2 schema fields changedv0.22.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20)"New value: +"Max results to return (default 20)"
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort field: \"created\" or \"modified\" (default \"modified\")"New value: +"Sort by \"created\" (frontmatter created timestamp) or \"modified\" (filesystem mtime). Default \"modified\". Notes without a created property are excluded from created-sorted results."
  8. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this read-only and idempotent, and the description adds valuable behavior beyond that: 'created' sorts notes without the property last rather than excluding them, 'modified' catches sync touches and property changes, and an empty vault returns an empty array. These behavioral details will help an agent predict results accurately.

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 organized into clear sections: overview, examples, when to use, parameter interactions, errors, and return format. It is longer than a one-liner, but every sentence adds needed operational context, and the core purpose is front-loaded.

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 having no output schema, the description fully documents the return shape: JSON array of note metadata with field names and nullability. It also covers empty-vault behavior and parameter edge cases, so an agent has enough information to call and interpret the tool correctly.

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?

Although the input schema already covers parameter names and defaults, the description explains how sort_by and limit interact, including the pitfall that a small limit with sort_by 'created' may return only notes that have the property. This adds important meaning beyond the schema's minimal 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?

The description states a specific verb and resource: 'List recently modified or created notes, sorted by timestamp.' It also distinguishes itself from a date-range filter and shows examples, making the tool's purpose unambiguous and distinct from sibling search tools.

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 includes a dedicated 'When to use' section and explicitly names alternatives: 'Prefer vault_search for content-based discovery. Prefer vault_search_by_folder for browsing a specific folder.' This gives clear routing guidance and conditions for choosing this tool versus siblings.

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