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. 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

Name	Required	Description
`confirm`	No	Ignored; kept for older clients.
`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

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 24, 2026

changedInput schema / properties / confirm / description

Previous value: -"Set to true to actually delete. Defaults to false, which returns a preview and deletes nothing."New value: +"Ignored; kept for older clients."

Changed1 schema field changedOct 10, 2026
- addedOutput schema / properties / next_actions / items
```
Added value: +{
+  "type": "object"
+}
```

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.4/5.0

Behavior4/5

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

Goes well beyond the annotations: discloses soft-delete semantics, the 30-day purge window, user recoverability, the specific refusal error code, and post-delete re-read verification with an 'unverified' outcome. This usefully qualifies the blunt destructiveHint=true. Minor gaps only: no mention that `confirm` is ignored, and no note on permissions/account selection.

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?

Front-loaded with the action and the two lookup modes, and each sentence adds real information about side effects or verification. Slight redundancy with the schema on the note_name tie-breaking rule and a dense final VERIFIED sentence keep it from a 5.

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, so return shape needn't be explained, yet the description still covers the outcomes an agent must reason about (soft delete, refusal, unverified). For a destructive 3-parameter tool, nothing needed to call it safely is missing.

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 coverage is 100% and the schema already states the exact-title and first-match caveats, so most of the description's parameter content is repetition. The one added value is pointing to list_notes/search_notes as the source of note_id; the ignored `confirm` parameter is explained only in the schema, not the description. Baseline 3 fits.

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?

Specific verb + resource ("Deletes a note from Apple Notes") plus the two ways to identify the target (ID or exact title). It also names the sibling tools that supply the note_id, so an agent can distinguish it from update_note or read_note 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?

Gives explicit routing ("Find note_id with list_notes or search_notes"), a preference rule (prefer note_id when titles collide), and a clear when-not case: notes already in Recently Deleted are refused with note_already_deleted because a second delete would be permanent.

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.