Skip to main content
Glama
aleksakarac

Obsidian MCP Extended

by aleksakarac

update_note_tool

Update or append markdown content in an existing Obsidian note. Replace entire content or add to the end, with option to create note if missing.

Instructions

Update the content of an existing note.

⚠️ IMPORTANT: By default, this REPLACES the entire note content. Always read the note first if you need to preserve existing content.

When to use:

  • Updating a note with completely new content (replace)

  • Adding content to the end of a note (append)

  • Programmatically modifying notes

When NOT to use:

  • Making small edits (read first, then update with full content)

  • Creating new notes (use create_note instead)

Returns: Update status with path, metadata, and operation performed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the note to update
contentYesNew markdown content (REPLACES existing content unless using append)
create_if_not_existsNoCreate the note if it doesn't exist
merge_strategyNoHow to handle content: 'replace' overwrites, 'append' adds to endreplace
ctxNo
Behavior5/5

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

With no annotations, the description fully discloses default replace behavior, the merge_strategy parameter, and return value. The warning about replacement is prominently highlighted.

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?

Concise with clear sections and bold/emoji for emphasis. Every sentence adds value, with no fluff.

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 no output schema, the description adequately describes return value (update status, path, metadata, operation). Covers all key behaviors and edge cases.

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 high (80%), but the description adds value by emphasizing the replace behavior and merge options beyond schema definitions. The ctx parameter lacks description but is less critical.

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 clearly states 'Update the content of an existing note' and specifies operations like replace and append. It distinguishes from sibling tool 'create_note' by noting when not to use it.

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?

Explicitly lists when to use (new content, append, programmatic) and when not to use (small edits, creating new notes). Includes important prerequisite: 'Always read the note first if you need to preserve existing content.'

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/aleksakarac/obsidian-mcp'

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