Skip to main content
Glama
rps321321

obsidian-mcp-pro

by rps321321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete Note

delete_note
Destructive

Remove a note by moving it to the vault's .trash for recovery, or delete it permanently from disk and optionally strip links to it across the vault.

Instructions

Delete a note. By default the file is moved to the vault's .trash folder (recoverable inside Obsidian); pass permanent=true to unlink it from disk immediately. When permanent=true, you can additionally pass removeReferences=true to strip wikilinks and markdown links to the deleted file across the vault (embeds are removed entirely; plain links fall back to their visible text). References are never rewritten when the file moves to .trash, since trashed files are recoverable.

Input Schema

NameRequiredDescriptionDefault
pathYesRelative path from vault root to the note to delete (e.g., 'archive/old.md'). Extension optional.
confirmNoSafety latch: must be set to true when permanent=true to confirm the caller intends irreversible deletion. Ignored when permanent=false (trash deletes are recoverable). If permanent=true and confirm is not true, the tool returns an error without deleting.
permanentNoIf true, delete the file permanently from disk; if false (default), move it to the vault's .trash folder so it can be recovered.
removeReferencesNoIf true (and permanent=true), strip wikilinks and markdown links pointing at the deleted file across the vault. Embeds are removed entirely; plain links fall back to their visible text (alias if present, else the deleted file's basename). Ignored when permanent=false. Default false — opt in explicitly because the rewrite is irreversible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.0.0
  3. Removedv1.9.0
  4. Changed1 schema field changedv1.5.2
    • addedInput schema / properties / removeReferences
      Added value: +{
+  "default": false,
+  "description": "If true (and permanent=true), strip wikilinks and markdown links pointing at the deleted file across the vault. Embeds are removed entirely; plain links fall back to their visible text (alias if present, else the deleted file's basename). Ignored when permanent=false. Default false — opt in explicitly because the rewrite is irreversible.",
+  "type": "boolean"
+}
  5. Addedv0.1.6
  6. Removedv0.1.4
  7. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / path / description
      Previous value: -"Relative path to the note"New value: +"Relative path from vault root to the note to delete (e.g., 'archive/old.md'). Extension optional."
    • changedInput schema / properties / permanent / description
      Previous value: -"If true, permanently delete instead of moving to trash"New value: +"If true, delete the file permanently from disk; if false (default), move it to the vault's .trash folder so it can be recovered."
  8. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the crucial nuance that the default action is recoverable via the vault's .trash, and that the truly irreversible path requires an explicit flag. It further discloses the side effects of removeReferences (embeds deleted entirely, plain links degraded to visible text or basename) — behavior an agent cannot infer from annotations alone.

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, front-loaded with the action, then the default behavior, then the opt-in escalation path. Nothing is repeated and every sentence carries a decision-relevant fact.

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?

For a destructive, four-parameter tool with no output schema, the description covers recoverability, irreversibility, and side effects of the reference-rewrite option, while the confirm safety latch is fully documented in the schema. An agent has everything needed to call it safely.

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%, and the schema's per-parameter text already explains permanent, confirm, and even the embed/link fallback semantics of removeReferences. The description largely restates that content rather than adding syntax, formats, or edge cases beyond it, so the baseline 3 applies.

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?

States a specific verb and resource ("Delete a note") and immediately scopes it into two distinct modes (trash-by-default vs. permanent unlink). No sibling tool in the list performs note deletion, so an agent can route here unambiguously without opening the schema.

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?

Gives explicit conditions for the optional behaviors: pass permanent=true only for immediate on-disk unlink, and removeReferences=true only in combination with permanent=true, with the rationale ("opt in explicitly because the rewrite is irreversible"). It also states the negative case (references are never rewritten when trashing). It stops short of naming an alternative tool (e.g. move_note) for relocating rather than deleting, which keeps it from a 5.

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