Skip to main content
Glama
ailenshen

Apple Notes MCP Server

delete_note

Remove a note from Apple Notes by specifying its title, optionally scoped to a folder. The deleted note is moved to the Recently Deleted folder for recovery.

Instructions

Delete a note from Apple Notes by title. Optionally specify folder to disambiguate. The note is moved to Recently Deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the note to delete
folderNoFolder name to scope the search

Implementation Reference

  • The function that executes the AppleScript command to delete a note.
    export async function deleteNote(title: string, folder?: string): Promise<void> {
      const folderClause = folder
        ? `of folder ${JSON.stringify(folder)}`
        : "";
    
      const script = `
    tell application "Notes"
      set matchedNotes to (every note ${folderClause} whose name is ${JSON.stringify(title)})
      if (count of matchedNotes) = 0 then
        error "Note not found: ${title.replace(/"/g, '\\"')}"
      end if
      delete item 1 of matchedNotes
    end tell
    `;
      await runAppleScript(script);
  • src/index.ts:136-153 (registration)
    MCP tool registration for 'delete_note'.
    server.tool(
      "delete_note",
      "Delete a note from Apple Notes by title. Optionally specify folder to disambiguate. The note is moved to Recently Deleted.",
      {
        title: z.string().describe("Title of the note to delete"),
        folder: z.string().optional().describe("Folder name to scope the search"),
      },
      async ({ title, folder }) => {
        try {
          await deleteNote(title, folder);
          return {
            content: [{ type: "text", text: `Note "${title}" deleted successfully.` }],
          };
        } catch (e: unknown) {
          return {
            content: [{ type: "text", text: `Error: ${(e as Error).message}` }],
            isError: true,
          };
Behavior4/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 effectively explains that deletion moves the note to 'Recently Deleted' rather than permanent removal, which is crucial behavioral context not inferable from the schema. It could improve by mentioning permissions or error cases, but it covers the key destructive action clearly.

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 extremely concise and front-loaded, with two sentences that efficiently convey the action, parameters, and outcome. Every word earns its place, and there's no redundant or vague language, making it easy for an agent to parse quickly.

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

Completeness4/5

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

Given the tool's complexity (a destructive operation with 2 parameters), no annotations, and no output schema, the description is mostly complete. It explains the deletion behavior and parameter usage well, but could benefit from mentioning potential errors (e.g., if the note doesn't exist) or the response format, slightly limiting completeness.

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 already documents both parameters ('title' and 'folder'). The description adds minimal value beyond the schema by implying the folder parameter's purpose ('to disambiguate'), but doesn't provide additional syntax or format details. This meets the baseline for high schema coverage.

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 from Apple Notes'), identifies the resource ('by title'), and distinguishes it from siblings like 'update_note' or 'get_note' by focusing on deletion. It provides a complete verb+resource+scope statement that leaves no ambiguity about the tool's function.

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 provides clear context for usage ('Optionally specify folder to disambiguate'), which helps differentiate when to use this tool versus alternatives like 'search_notes' for finding notes. However, it doesn't explicitly state when NOT to use it (e.g., for permanent deletion vs. moving to Recently Deleted) or name specific alternatives, keeping it from a perfect score.

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/ailenshen/apple-notes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server