Skip to main content
Glama
Dan8Oren

mcp-apple-notes

list-notes

List Apple Notes by folder path, retrieving title, path, and timestamps. Optionally include note content for complete access to your notes data.

Instructions

List Apple Notes with title, path, and timestamps. Optionally filter by folder path and include note content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOptional folder path to filter notes (e.g. iCloud/Work/Projects). Use list-folders to get available paths.
includeContentNoIf true, include note content in the response (default: false)

Implementation Reference

  • Handler that dispatches 'list-notes' tool calls. Parses args with ListNotesSchema, then either filters by folder path (via getNotesByPath) or returns all indexed notes (via getIndexedNotes).
    } else if (name === "list-notes") {
      const { path, includeContent } = ListNotesSchema.parse(args);
      const notes = path
        ? await getNotesByPath(path, includeContent)
        : await getIndexedNotes(notesTable, includeContent);
      return createJsonResponse({ ok: true, data: notes });
  • Zod schema for list-notes input validation: optional 'path' folder filter and optional 'includeContent' boolean.
    const ListNotesSchema = z.object({
      path: z.string().optional(),
      includeContent: z.boolean().optional(),
    });
  • index.ts:202-221 (registration)
    Tool registration within the ListToolsRequestSchema handler, defining the tool name, description, and input schema for the MCP server.
    {
      name: "list-notes",
      description:
        "List Apple Notes with title, path, and timestamps. Optionally filter by folder path and include note content.",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description:
              "Optional folder path to filter notes (e.g. iCloud/Work/Projects). Use list-folders to get available paths.",
          },
          includeContent: {
            type: "boolean",
            description: "If true, include note content in the response (default: false)",
          },
        },
        required: [],
      },
    },
  • Helper that uses JXA (JavaScript for Automation) to query Apple Notes by folder path, returning note metadata and optionally content.
    const getNotesByPath = async (folderPath: string, includeContent = false) => {
      const result = await verboseRunJxa(
        `${jxaGetFolderPath}
        const app = Application('Notes');
        app.includeStandardAdditions = true;
        const targetPath = args[0];
        const withContent = args[1] === 'true';
        const allFolders = Array.from(app.folders());
        const folder = allFolders.find(f => getFolderPath(f) + '/' + f.name() === targetPath);
        if (!folder) return JSON.stringify([]);
        const notes = Array.from(folder.notes());
        return JSON.stringify(notes.map(note => {
          const base = {
            id: note.id(),
            title: note.name(),
            path: targetPath,
            creation_date: note.creationDate().toLocaleString(),
            modification_date: note.modificationDate().toLocaleString()
          };
          if (withContent) base.content = note.body();
          return base;
        }));`,
        [folderPath, String(includeContent)]
      );
    
      return JSON.parse(result as string) as {
        id: string;
        title: string;
        path: string;
        creation_date: string;
        modification_date: string;
        content?: string;
      }[];
  • Helper that returns all notes from the local LanceDB index, optionally including content.
    export const getIndexedNotes = async (notesTable: lancedb.Table, includeContent = false) => {
      const rows = await notesTable.query().toArray();
      return rows.map((row: any) => ({
        id: row.id,
        title: row.title,
        path: row.path,
        creation_date: row.creation_date,
        modification_date: row.modification_date,
        ...(includeContent ? { content: row.content } : {}),
      }));
    };
Behavior3/5

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

No annotations provided; the description implies a read-only operation but does not explicitly state safety, rate limits, or performance implications of including content.

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?

One concise sentence that immediately states the core purpose, with no wasted words.

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?

For a simple list tool, the description covers the return fields (title, path, timestamps) and optional parameters. It lacks pagination details and does not reference related tools like index-notes, but remains adequate.

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 clear descriptions for both parameters. The description restates the optional filtering and content inclusion, adding no new semantic value beyond the schema.

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 tool lists Apple Notes with specific fields (title, path, timestamps), and distinguishes it from sibling tools like get-note (single note) and search-notes (search).

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 tells when to use it (listing notes, optionally filtering by folder and including content) but does not explicitly mention when not to use it or alternatives like search-notes for full-text search.

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