mcp-apple-notes

delete_note

Delete a note from Apple Notes by moving it to Recently Deleted, recoverable for 30 days.

Instructions

Elimina una nota de Notes.app. Igual que borrar desde la UI: la nota se mueve a 'Recently Deleted' y es recuperable ahí por ~30 días, no se borra instantáneamente.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_note"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Id de la nota a eliminar.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description fully discloses the non-instantaneous deletion behavior—soft delete to 'Recently Deleted' with a ~30-day recovery window. This is critical behavioral context that the agent needs to know.

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 two sentences, front-loaded with the action, then briefly explaining the consequence. No wasted words, efficient and clear.

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?

For a simple delete operation with one required parameter and no output schema, the description provides complete context: what the tool does, the soft-delete behavior, and recovery window. No gaps.

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% with a clear description for the single 'id' parameter. The description adds no extra meaning beyond the schema, so a baseline 3 is appropriate.

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 action 'Elimina una nota de Notes.app' (deletes a note from Notes.app). It uses a specific verb and resource, and is distinct from sibling tools (create, list, read, search, update).

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 explains that the deletion mimics UI behavior: note moves to 'Recently Deleted' with ~30-day recovery. This provides context for the tool's effect, helping the agent decide when to use it, though no explicit alternatives or exclusions are given.

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

Deploy Server