Skip to main content
Glama
Dan8Oren

mcp-apple-notes

create-note

Add a note to Apple Notes with a title and markdown content. Optionally organize by placing it in a specific folder path.

Instructions

Create a new Apple Note with a title and markdown content. Optionally place it in a folder path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
contentYesNote content in markdown format
folderNoOptional folder path to create the note in (e.g. iCloud/Work/Projects). Use list-folders to get available paths.

Implementation Reference

  • Request handler for create-note - parses args, calls createNote, re-indexes, returns response
    if (name === "create-note") {
      const { title, content, folder } = CreateNoteSchema.parse(args);
      const noteId = await createNote(title, markdownToHtml(content), folder);
      const note = await refreshIndexedNoteById(notesTable, noteId);
      return createJsonResponse({
        ok: true,
        data: note,
        message: `Created note "${title}"${folder ? ` in ${folder}` : ""}.`,
      });
  • Actual implementation that uses JXA (AppleScript) to create a macOS Apple Note with title, HTML body, and optional folder
    const createNote = async (title: string, content: string, folder?: string) => {
      const result = await verboseRunJxa(
        `${jxaGetFolderPath}
        const app = Application('Notes');
        const targetPath = args[2];
        const note = app.make({new: 'note', withProperties: {
          name: args[0],
          body: args[1]
        }});
        if (targetPath) {
          const allFolders = Array.from(app.folders());
          const targetFolder = allFolders.find(f => getFolderPath(f) + '/' + f.name() === targetPath);
          if (!targetFolder) throw new Error('__FOLDER_NOT_FOUND__:' + targetPath);
          app.move(note, {to: targetFolder});
        }
        return note.id();`,
        [title, content, folder || ""]
      );
      return result as string;
    };
  • Zod schema defining the input shape for create-note: title (required), content (required), folder (optional)
    const CreateNoteSchema = z.object({
      title: z.string(),
      content: z.string(),
      folder: z.string().optional(),
    });
  • index.ts:258-278 (registration)
    Tool registration in ListToolsRequestSchema handler, defining the tool name, description, and JSON schema input
    {
      name: "create-note",
      description:
        "Create a new Apple Note with a title and markdown content. Optionally place it in a folder path.",
      inputSchema: {
        type: "object",
        properties: {
          title: { type: "string" },
          content: {
            type: "string",
            description: "Note content in markdown format",
          },
          folder: {
            type: "string",
            description:
              "Optional folder path to create the note in (e.g. iCloud/Work/Projects). Use list-folders to get available paths.",
          },
        },
        required: ["title", "content"],
      },
    },
  • Converts markdown content to HTML before passing to the Apple Notes JXA API
    const { turndown } = new TurndownService();
    const markdownToHtml = (md: string) => marked(md, { async: false }) as string;
    const db = await lancedb.connect(path.join(os.homedir(), ".mcp-apple-notes", "data"));
Behavior2/5

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

With no annotations, the description must handle transparency. It only indicates creation and optional folder placement but fails to disclose behavior such as duplicate handling, character limits, success/failure responses, or what happens if the folder path does not exist.

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?

A single, concise sentence conveys the core functionality without extraneous words or repetition. It is well-structured and front-loaded.

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

Completeness2/5

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

The description is incomplete for a creation tool with no output schema. It omits what the tool returns (e.g., note ID), how the folder is handled if missing, and any potential side effects. It also does not leverage sibling tools like list-folders for context.

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 67% (2 of 3 parameters have descriptions). The description mentions all three parameters but adds minimal new information: it restates that content is in markdown (already in schema) and folder is optional (already in schema). It does clarify the title's role but lacks detailed constraints.

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 verb 'Create' and the resource 'Apple Note' with specific details: title, markdown content, and optional folder placement. It effectively distinguishes from sibling tools like edit-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?

No guidance is provided on when to use this tool versus alternatives (e.g., append-to-note, edit-note). There is no mention of prerequisites, exclusions, or best practices, leaving the agent to infer appropriate contexts.

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