Skip to main content
Glama

Move/Rename Note

move_note
Destructive

Move or rename a note within your Obsidian vault, preserving content and automatically creating destination folders. Optionally update all internal links to point to the new location, or skip for faster operation on large vaults.

Instructions

Move or rename a note within the vault, preserving its full content. Parent folders at the destination are created as needed. By default, wikilinks and file references are updated, matching Obsidian's "Automatically update internal links" behavior. Pass updateLinks: false to skip the rewrite scan (faster on large vaults; pair with find_broken_links if you need to audit afterward). A .md extension is added automatically if omitted from either path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oldPathYesCurrent relative path of the note from vault root (e.g., 'inbox/idea.md')
newPathYesDestination relative path from vault root (e.g., 'projects/idea.md'). Creates intermediate folders as needed.
updateLinksNoIf true (default), update every wikilink, markdown link, and canvas node reference across the vault to point at the new path. Set false to skip the rewrite pass.
Behavior5/5

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

Beyond annotations (destructiveHint=true), description details automatic folder creation, link updating behavior, .md extension handling, and optional skip of rewrite scan. No contradiction with 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?

Four sentences, each with clear purpose: action, folder creation, link update behavior, and extension handling. Front-loaded with main purpose, no redundant information.

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?

Fully addresses the tool's behavior considering no output schema. Covers all key aspects: content preservation, destination creation, link updates, and extension handling. No missing details for correct invocation.

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 100%, but description adds value by explaining default updateLinks behavior, automatic .md extension, and folder creation. Though baseline is 3, the additional context merits a 4.

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 'Move or rename a note within the vault' with a specific verb and resource. It distinguishes from sibling tools like create_note, delete_note, and append_to_note by focusing on relocation and renaming.

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

Usage Guidelines4/5

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

Describes when to use with default link updating, and when to set updateLinks: false for speed, even suggesting pairing with find_broken_links. However, does not explicitly state when not to use or contrast with similar operations like copy.

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

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