Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by JujiuYey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_note

Modify notes in your Obsidian vault by replacing or appending content, and update metadata such as title, tags, and aliases.

Instructions

Update the content or metadata of a note

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "update_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the note file
tagsNoNew tags (optional, replaces existing)
titleNoNew title (optional, updates frontmatter)
appendNoWhether to append content instead of replacing
aliasesNoNew aliases (optional, replaces existing)
contentNoNew content to replace (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Update' without revealing that content may be replaced or appended, that tags/aliases are replaced, or whether changes are reversible. The schema hints at these behaviors, but the description itself adds no value beyond a generic operation.

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 a single, front-loaded sentence of eight words, perfectly concise with no wasted words. It efficiently communicates the core function without redundancy.

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

Completeness2/5

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

For a tool with 6 parameters and no output schema or annotations, the description is incomplete. It does not explain return values, side effects, append behavior, or when partial updates are allowed. The user must rely entirely on the schema to infer usage, which is insufficient for a mutation tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with each parameter described. The description's phrase 'content or metadata' loosely maps to content, title, tags, and aliases, but adds no new meaning beyond what the schema already provides. Baseline 3 is appropriate given the high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'update' with a clear resource 'a note', and mentions content or metadata. It distinguishes itself from siblings like create_note and delete_note by implying modification of an existing note. However, it does not explicitly state the scope (e.g., partial versus full update), which prevents a perfect score.

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

Usage Guidelines3/5

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

The description implies usage for modifying existing notes, which differentiates it from create_note and delete_note. However, it provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context is clear but not formally stated.

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

Deploy Server

Other Tools