Skip to main content
Glama
Dan8Oren

mcp-apple-notes

append-to-note

Append markdown content to an existing Apple Note. Identify the note by its note ID, title, or folder path to disambiguate duplicate titles.

Instructions

Append content to the end of an existing Apple Note. Identify note by noteId or title.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdNoApple Notes ID. If provided, skips title resolution.
titleNoTitle of the note to append to
pathNoOptional folder path to disambiguate duplicate titles
contentYesContent in markdown format to append to the end of the note

Implementation Reference

  • The core handler function that executes the append-to-note logic. It uses JXA (JavaScript for Automation) to find the note by ID, get its current body, and set the body to currentBody + contentToAppend. Note that it appends raw HTML content (already converted from markdown by the caller).
    const appendToNote = async (noteId: string, content: string) => {
      await verboseRunJxa(
        `const app = Application('Notes');
        const noteId = args[0];
        const contentToAppend = args[1];
        const note = Array.from(app.notes()).find(note => {
          return note.id() === noteId;
        });
        if (!note) throw new Error('__NOTE_NOT_FOUND__:' + noteId);
        const currentBody = note.body();
        note.body = currentBody + contentToAppend;
        note.name = note.name();
        return true;`,
        [noteId, content]
      );
    };
  • Zod schema for validating append-to-note input. Accepts optional noteId, title, path and required content. Requires either noteId or title.
    const AppendToNoteSchema = z
      .object({
        noteId: z.string().optional(),
        title: z.string().optional(),
        path: z.string().optional(),
        content: z.string(),
      })
      .refine((d) => d.noteId || d.title, { message: "Either noteId or title must be provided" });
  • index.ts:304-327 (registration)
    Tool registration metadata in the ListToolsRequestSchema handler. Defines the name, description, and input schema that is exposed to MCP clients.
    {
      name: "append-to-note",
      description:
        "Append content to the end of an existing Apple Note. Identify note by noteId or title.",
      inputSchema: {
        type: "object",
        properties: {
          noteId: {
            type: "string",
            description: "Apple Notes ID. If provided, skips title resolution.",
          },
          title: { type: "string", description: "Title of the note to append to" },
          path: {
            type: "string",
            description: "Optional folder path to disambiguate duplicate titles",
          },
          content: {
            type: "string",
            description: "Content in markdown format to append to the end of the note",
          },
        },
        required: ["content"],
      },
    },
  • index.ts:17-23 (registration)
    List of mutating tools, including append-to-note, used to filter tools in read-only mode.
    const MUTATING_TOOLS = new Set([
      "create-note",
      "edit-note",
      "append-to-note",
      "move-note",
      "delete-note",
    ]);
  • The CallToolRequestSchema handler that routes 'append-to-note' calls. It parses arguments with AppendToNoteSchema, resolves the note via resolveNoteId, calls appendToNote with HTML-converted content, refreshes the index, and returns the result.
    } else if (name === "append-to-note") {
      const { noteId, title, path, content } = AppendToNoteSchema.parse(args);
      const { note: resolvedNote } = await resolveNoteId(notesTable, noteId, title, path);
      await appendToNote(resolvedNote.id, markdownToHtml(content));
      const note = await refreshIndexedNoteById(notesTable, resolvedNote.id);
      return createJsonResponse({
        ok: true,
        data: note,
        message: `Appended content to "${resolvedNote.title}".`,
      });
    } else if (name === "move-note") {
Behavior3/5

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

The description discloses that content is appended 'to the end' and that the note must exist, but lacks details on error handling (e.g., note not found), permission requirements, or return behavior. Without annotations, this is adequate but not thorough.

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?

Two sentences concisely convey the purpose and identification method without unnecessary words. Every part of the description adds value.

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

Completeness3/5

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

For a simple append tool, the description covers the core action. However, it omits what happens on failure (e.g., duplicate title, missing note) and does not clarify return values. With no output schema, more context would be helpful.

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 descriptions for each parameter. The description adds little beyond stating identification by noteId or title, which is already clear from the schema. Baseline of 3 is appropriate given 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 action (append), the target resource (existing Apple Note), and how to identify it (by noteId or title). This effectively distinguishes it from siblings like create-note or delete-note.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives (e.g., edit-note) or mention any prerequisites or exclusions. The agent must infer usage context from the tool name and schema alone.

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

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