Engram Obsidian Memory Sync

Delete Note

delete_note

DestructiveIdempotent

Delete one note by path: it moves to trash, restorable with restore_deleted for 7 days on Free and 30 on paid plans, following your plan at the time (a downgrade shortens it; the result says until when). The deletion syncs to all connected Obsidian devices. Deleting a path that holds no note succeeds and reports deleted: false. To remove a whole folder use delete_folder. To move a note instead use rename_note. For an image, PDF, or other binary file use delete_attachment.

Input Schema

Name	Required	Description	Default
`path`	Yes	Path of the note to delete
`vault_id`	No	Target vault: its name (e.g. "Engram") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve.

Output Schema

Name	Required	Description
`path`	Yes
`deleted`	Yes	false when no note existed at that path
`delete_op_id`	Yes	Pass to restore_deleted to undo this call; null when nothing was removed
`restorable_until`	Yes	ISO 8601 time this delete stops being restorable on your current plan; a plan change moves it

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedOutput schema / properties / delete_op_id

Added value: +{
+  "description": "Pass to restore_deleted to undo this call; null when nothing was removed",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / restorable_until

Added value: +{
+  "description": "ISO 8601 time this delete stops being restorable on your current plan; a plan change moves it",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "path",
-  "deleted"
-]New value: +[
+  "path",
+  "deleted",
+  "delete_op_id",
+  "restorable_until"
+]

Changed1 schema field changedSep 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / vault_id / description

Previous value: -"Target vault — its name (e.g. \"Engram\") or its UUID. REQUIRED when you own more than one vault — the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve."New value: +"Target vault: its name (e.g. \"Engram\") or its UUID. REQUIRED when you own more than one vault; the server keeps no active-vault state between calls, so it must be passed on every vault-scoped call. Omit only if you have a single vault. Call list_vaults if a name does not resolve."

First observedSep 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare destructive/idempotent but the description carries the real behavioral payload: deletion is reversible via restore_deleted, retention is 7 days on Free and 30 on paid, the window follows the plan at deletion time and can be shortened by a downgrade, the result reports the deadline, and the change syncs to all connected devices. It also discloses the non-obvious edge case that deleting a path with no note succeeds with deleted: false, which prevents an agent from retrying or treating it as an error.

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 operation and its restorable-trash semantics are front-loaded, followed by edge case and then a compact block of sibling routing. Every sentence supplies distinct information — retention, sync, no-op success, or an alternative tool — with no filler.

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?

An output schema exists, yet the description still surfaces the two return facts an agent most needs (the recovery deadline and deleted: false). Combined with retention policy, cross-device sync, and sibling disambiguation, nothing needed to call this destructive tool safely is absent.

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% and vault_id already documents the multi-vault requirement in detail, so the baseline is 3. The description still adds meaning about the path parameter that the schema does not: a path holding no note is a valid, successful call that returns deleted: false, which tells the agent how to interpret path resolution failures.

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 with scope ('Delete one note by path') and immediately clarifies that it is a soft delete to trash. Explicitly distinguishes itself from delete_folder, rename_note, and delete_attachment, so an agent can separate it from its closest siblings without opening a schema.

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

Usage Guidelines5/5

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

Names three alternatives with the exact condition that should route to each: 'To remove a whole folder use delete_folder', 'To move a note instead use rename_note', 'For an image, PDF, or other binary file use delete_attachment.' When/when-not guidance is fully explicit rather than inferred.

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

All Engram Obsidian Memory Sync tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.