Local MCP

Delete Note

delete_note

Destructive

Deletes a note from Apple Notes, by ID or exact title. Like deleting it in the app, the note goes to "Recently Deleted" and Apple purges it after 30 days — the user can still recover it there. A note that is ALREADY in Recently Deleted is refused (note_already_deleted): deleting it again would erase it permanently. On a Mac where LMCP cannot check that (no Full Disk Access, and no earlier delete to learn the folder from) the preview carries a warning and the result says trash_check: not_verified. Requires confirm=true. The result is VERIFIED: the tool re-reads the note after deleting and reports the deletion as unverified if it is still where it was, so a success here means the note is really gone from list_notes/search_notes/read_note. Find note_id with list_notes or search_notes.

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	No	Set to true to actually delete. Defaults to false, which returns a preview and deletes nothing.
`note_id`	No	The note's id, as list_notes/search_notes report it.
`note_name`	No	Exact title, when you don't have the id. If several notes share it, the first match is deleted — prefer note_id.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`name`	No
`deleted`	No	True only when the deletion was VERIFIED by re-reading the note
`in_trash`	No	The note moved to Recently Deleted (Apple purges it after 30 days) rather than vanishing outright
`verified`	No	The note was re-read after deleting and is no longer where it was
`trash_check`	No	Present as 'not_verified' when LMCP could not check beforehand whether the note was already in Recently Deleted
`folder_after`	No	Where it ended up (present when it moved instead of vanishing)
`next_actions`	No
`folder_before`	No	The folder the note was in before deleting

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

addedOutput schema / properties / trash_check

Added value: +{
+  "description": "Present as 'not_verified' when LMCP could not check beforehand whether the note was already in Recently Deleted",
+  "type": "string"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / confirm / description

Added value: +"Set to true to actually delete. Defaults to false, which returns a preview and deletes nothing."

Changed1 schema field changedSep 29, 2026

removedInput schema / properties / confirm / description

Removed value: -"Set to true to actually delete. Defaults to false, which returns a preview and deletes nothing."

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / confirm / description

Added value: +"Set to true to actually delete. Defaults to false, which returns a preview and deletes nothing."

AddedAug 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes far beyond the destructiveHint=true annotation: it discloses the soft-delete semantics (Recently Deleted, 30-day purge, user-recoverable), the refusal behavior and its error code (note_already_deleted) that prevents permanent erasure, the Full Disk Access failure mode with trash_check: not_verified, and post-delete verification behavior. This is exactly the behavioral context an agent needs before firing a destructive call.

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?

A single dense paragraph that is front-loaded with the core action and the recoverability guarantee before moving to edge cases. Every sentence carries weight for a destructive tool, though it is longer than strictly minimal.

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?

Covers the operation, precondition, failure modes, recovery path, and verification guarantee; since an output schema exists it correctly avoids describing return payloads. An agent has everything needed to call this destructive tool safely.

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%, so baseline is 3, but the description adds real meaning: it reinforces that confirm must be true to act, explains how to obtain note_id, and notes the title-collision risk ('first match is deleted'). It slightly duplicates schema text but the operational framing adds value.

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 ('Deletes a note from Apple Notes, by ID or exact title'), which cleanly separates it from sibling delete tools (delete_reminder, gdrive_delete_file) and from update_note. An agent immediately knows the operation and the two addressing modes.

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?

Explicit when-to-use routing ('Find note_id with list_notes or search_notes'), an explicit when-not ('A note that is ALREADY in Recently Deleted is refused'), and a hard precondition ('Requires confirm=true'). Nothing is left to inference.

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

All Local MCP 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.