obsidian-mcp

obsidian_delete_note

DestructiveIdempotent

Remove a note safely by moving it to the vault's .trash for later restore, or choose permanent deletion when the note must be unrecoverable.

Instructions

Delete a note, by default into the vault's .trash folder.

A default delete is recoverable: the note moves to '.trash' inside the vault and can be restored from Obsidian. Pass permanent=true only when the note should be unrecoverable.

Args: params (DeleteNoteInput): - path (str): Vault-relative path to delete - permanent (bool): True deletes outright and cannot be undone

Returns: str: JSON of the shape {"status": "ok", "action": "trashed"|"deleted", "path": str, "backend": "rest"|"filesystem", "note": str} where path is the .trash location for a recoverable delete. On failure: "Error: "

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true unbeknownst to the description. It transparently discloses the trash and permanent behaviors, including recoverability implicationstelling the agent when to use each variant. A minor gap is not mentioning vault targeting, but that is covered in schema.

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 concise and front-loads the key behavior (default trash) in the first line. Additional details are organized logically with clear sections for parameters and return value. Every sentence adds value, no fluff.

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?

The output schema is described in detail, including the JSON shape and error semantics. Given the simplicity of the tool and the presence of clear annotations (destructiveHint=true), the description is complete enough for correct usage. It could mention the vault parameter but that is in 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?

The description repeats the schema definitions for path and permanent, but since schema coverage is 0%, it fully compensates by describing both parameters in plain language. It adds no new detail beyond what the schema already states, so baseline 3 is appropriate.

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 clearly states that the tool deletes a note by default into the vault's .trash folder, which is specific and distinguishes it from other note operations like write or move. Though it does not explicitly compare with siblings, the unique verb and resource are clear.

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?

The description explicitly explains when to use the default (recoverable delete) versus permanent=true, and it warns about irreversibility. It does not name alternative tools, but for a delete operation, the guidance is sufficient for correct selection and invocation.

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

Deploy Server