Skip to main content
Glama
yuchi-chang

obsidian-mcp

by yuchi-chang

Move or rename a note

obsidian_move_note
Destructive

Move or rename a note and automatically update all wikilinks across the vault.

Instructions

Moves or renames a note. Wikilinks across the vault are updated automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultNoVault name to target. Optional — defaults to the most recently focused vault.
fileNoNote name resolved as a wikilink (e.g. 'My Note'). Provide either `file` or `path`.
pathNoVault-root-relative path to the note (e.g. 'Folder/My Note.md'). Provide either `file` or `path`.
toYesDestination path (vault-relative). Include filename.
confirmNoSet to true to skip the interactive confirmation prompt. Use only when the caller has already confirmed with the user.
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds value by noting automatic wikilink updates, providing useful behavioral context beyond annotations.

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?

Two concise sentences that front-load the primary action. No unnecessary words; every sentence is essential.

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?

Covers the core behavior well. Lacks mention of return value or confirmation prompt behavior, but schema covers the confirm parameter. Adequate for a state-modifying tool with no output schema.

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 description coverage is 100%, so each parameter is already documented. The description adds no additional parameter-level details beyond what the schema provides.

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?

Clearly states the tool moves or renames a note and automatically updates wikilinks. Distinguishes from sibling tools like obsidian_create_note and obsidian_delete_note.

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?

Implied usage for moving/renaming notes, but no explicit guidance on when to use vs alternatives like obsidian_create_note or obsidian_delete_note. No when-not scenarios mentioned.

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

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