Skip to main content
Glama
maxkuminov

Obsidian MCP (pgvector + Ollama, self-hosted)

move_note

Move a note to a new path in the vault, automatically updating metadata and backlinks. Optionally rewrite wikilinks in linked notes.

Instructions

Move or rename a note inside the vault. Requires a readwrite API key.

Updates notes_metadata.file_path for the moved note and note_links.target_path rows whose stored target matched the old path. Backlinks via target_note_id keep working without rewriting source notes (the moved note's id is unchanged).

With rewrite_links=True, also opens every source note that linked to this note and rewrites the link title in-place: [[Old]][[New]], [[Old|alias]][[New|alias]], [[Old#anchor]][[New#anchor]], ![[Old]]![[New]], and path-style [[folder/Old]][[new/folder/New]]. Aliases and anchors are preserved; only the title portion is rewritten.

Writes are atomic. See get_vault_guide for vault folder conventions.

Args: from_path: Vault-relative path of the existing note. to_path: Vault-relative path of the destination. Must not exist. Parent directories are created automatically. rewrite_links: If True, also rewrite incoming wikilinks and embeds in source notes. Off by default — opting in is destructive (it modifies other notes' bodies).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_pathYes
to_pathYes
rewrite_linksNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so the description fully carries the transparency burden. It details side effects on notes_metadata, note_links, and the optional link rewriting with precise transformation patterns. Also notes atomic writes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with the core action and key requirements. It is slightly lengthy but every sentence provides valuable information. Could be slightly more concise without losing detail.

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?

Output schema exists but is not detailed here; however, the description is complete for understanding behavior and parameters. Covers prerequisites, side effects, and parameter constraints adequately for any AI agent to use the tool correctly.

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

Parameters5/5

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

Input schema has 0% description coverage, but the description explains each parameter in depth: from_path and to_path with constraints (must exist, must not exist, parent directories auto-created), rewrite_links with default false and destructive note.

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 starts with 'Move or rename a note inside the vault', which clearly states the action and resource. It distinguishes from sibling tools like create_note, delete_note, edit_note by focusing on path modifications.

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?

Mentions requirement of a readwrite API key and warns about the destructive nature of rewrite_links. Does not explicitly compare to alternatives but context implies it's for moving/renaming, not editing 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/maxkuminov/obsidian-mcp'

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