Skip to main content
Glama
adrienthebo
by adrienthebo

update_note_tool

Modify existing Obsidian notes by replacing or appending content programmatically. Use to update notes with new information or add content to the end of files.

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
pathYesWhich note to update in your vault
contentYesNew content for the note. By default this REPLACES all existing content. Use merge_strategy='append' to add to the end instead.
create_if_not_existsNoAutomatically create the note if it doesn't exist yet
merge_strategyNoHow to handle existing content. 'replace' = overwrite everything (default), 'append' = add new content to the endreplace
ctxNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: the default destructive behavior ('REPLACES the entire note content'), the need to read first to preserve content, and the return format ('Update status with path, metadata, and operation performed'). However, it lacks details on permissions, rate limits, or error handling, leaving some gaps.

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 well-structured and front-loaded, starting with the core purpose followed by important warnings and usage guidelines. Each sentence earns its place: the first states the action, the warning highlights critical behavior, and the bullet points provide clear context without redundancy. It's appropriately sized for a tool with multiple parameters and behavioral nuances.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters, no annotations, no output schema), the description does a good job covering key aspects: purpose, usage, behavioral traits, and some parameter context. However, it doesn't fully explain the return values beyond a brief mention, and with no output schema, more detail on the 'Update status' would be helpful. It's mostly complete but has minor gaps.

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 high at 80%, setting a baseline of 3. The description adds value by explaining the default behavior ('REPLACES the entire note content') and mentioning the 'append' option for 'merge_strategy', which complements the schema. It also implicitly clarifies that 'path' identifies the note and 'content' is the new text, though it doesn't detail all parameters like 'create_if_not_exists' or 'ctx'.

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 the verb ('Update') and resource ('content of an existing note'), making the purpose specific. It distinguishes from sibling tools like 'create_note_tool' (for creating new notes) and 'edit_note_section_tool' (for small edits), which helps differentiate its role in the toolset.

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 provides explicit guidance with dedicated 'When to use' and 'When NOT to use' sections. It specifies scenarios like replacing content, appending, and programmatic modifications, while warning against small edits (suggesting 'read first') and directing to 'create_note' for new notes. This clearly defines when to choose this tool over alternatives.

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

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