Skip to main content
Glama

delete_note

Remove notes from your Obsidian vault by specifying a file path, with options to permanently delete or move to trash for recovery.

Instructions

Delete a note (moves to vault trash by default)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative path to the note
permanentNoIf true, permanently delete instead of moving to trash

Implementation Reference

  • The actual logic for deleting a note, supporting both trash and permanent deletion.
    export async function deleteNote(
      vaultPath: string,
      relativePath: string,
      useTrash = true,
    ): Promise<void> {
      const fullPath = resolveVaultPath(vaultPath, relativePath);
    
      if (useTrash) {
        const trashDir = path.join(vaultPath, ".trash");
        const trashPath = path.join(trashDir, relativePath);
        const resolvedTrash = path.resolve(trashPath);
        const resolvedTrashDir = path.resolve(trashDir);
        if (!resolvedTrash.startsWith(resolvedTrashDir + path.sep) && resolvedTrash !== resolvedTrashDir) {
          throw new Error(`Invalid trash path: ${relativePath}`);
        }
        await fs.mkdir(path.dirname(trashPath), { recursive: true });
        await fs.rename(fullPath, trashPath);
      } else {
        await fs.unlink(fullPath);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the default trash behavior, which is useful, but lacks details on permissions, error handling (e.g., if the note doesn't exist), rate limits, or whether deletion is reversible. For a mutation tool, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence with zero waste. It is front-loaded with the core action ('Delete a note') and includes essential context ('moves to vault trash by default') without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a deletion tool with no annotations and no output schema, the description is incomplete. It does not cover error cases, return values, or safety considerations (e.g., confirmation prompts). For a tool that modifies data, more context is needed to ensure proper usage.

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 the schema fully documents the parameters. The description adds no additional meaning beyond what the schema provides, such as explaining the implications of 'permanent' deletion versus trash. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 the specific action ('Delete a note') and distinguishes it from siblings by specifying the default behavior ('moves to vault trash by default'). This differentiates it from tools like 'move_note' or 'create_note' by focusing on deletion with a trash mechanism.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing the note to exist, or compare it to siblings like 'move_note' for relocation instead of deletion. Usage is implied but not explicitly stated.

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