Skip to main content
Glama
ailenshen

Apple Notes MCP Server

get_note

Retrieve Apple Notes content as Markdown by specifying a note title, with optional folder filtering to locate specific notes.

Instructions

Get the full content of a note by its title, returned as Markdown. Optionally specify folder to disambiguate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNote title (exact match)
folderNoFolder name to scope the search

Implementation Reference

  • Tool registration and handler implementation for "get_note". It calls the `getNoteBody` function from `applescript.ts`.
    server.tool(
      "get_note",
      "Get the full content of a note by its title, returned as Markdown. Optionally specify folder to disambiguate.",
      {
        title: z.string().describe("Note title (exact match)"),
        folder: z.string().optional().describe("Folder name to scope the search"),
      },
      async ({ title, folder }) => {
        try {
          const body = await getNoteBody(title, folder);
          return {
            content: [{ type: "text", text: body }],
          };
        } catch (e: unknown) {
          return {
            content: [{ type: "text", text: `Error: ${(e as Error).message}` }],
            isError: true,
          };
        }
      }
    );
  • Actual implementation of the `getNoteBody` function which runs the AppleScript to retrieve and convert note content from Apple Notes.
    export async function getNoteBody(title: string, folder?: string): Promise<string> {
      const folderClause = folder
        ? `of folder ${JSON.stringify(folder)}`
        : "";
    
      // Try to find by exact title; if folder is given, scope to that 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
      return body of item 1 of matchedNotes
    end tell
    `;
      const html = await runAppleScript(script);
      return turndown.turndown(html);
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the exact match requirement for the title and the optional folder for disambiguation, which are behavioral traits. However, it lacks details on error handling (e.g., what happens if the note isn't found), permissions, or rate limits, leaving gaps for a read operation.

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 with zero waste: the first sentence states the core purpose and output format, and the second adds crucial context for the optional parameter. It is front-loaded and appropriately sized for a simple tool.

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 low complexity (read operation, 2 parameters, no output schema), the description is mostly complete. It covers the purpose, key constraints, and parameter usage. However, without annotations or output schema, it could benefit from mentioning error cases or response format, though not strictly required for a basic get tool.

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 well. The description adds marginal value by clarifying that the folder is for disambiguation, but does not provide additional syntax or format details beyond what the schema specifies (e.g., folder name format). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Get the full content'), resource ('a note'), and key constraint ('by its title'), distinguishing it from siblings like list_notes (list) or search_notes (search). It specifies the output format ('returned as Markdown'), which is not obvious from the name alone.

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 when to use the tool: to retrieve a specific note by title, with optional folder disambiguation. It implies usage vs. siblings (e.g., use list_notes to browse, search_notes for fuzzy matching), but does not explicitly name alternatives or state when not to use it.

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