Skip to main content
Glama

notes_list

List all Apple Notes or filter by folder to organize and access your notes directly from macOS applications.

Instructions

[Apple Notes operations] List all notes or notes in a specific folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoOptional folder name to list notes from

Implementation Reference

  • Handler function that generates AppleScript code to list all notes or notes in a specific folder in Apple Notes.app.
    script: (args) => {
      const { folder = "" } = args;
      
      if (folder) {
        return `
          tell application "Notes"
            set folderList to folders whose name is "${folder}"
            if length of folderList > 0 then
              set targetFolder to item 1 of folderList
              set noteNames to name of notes of targetFolder
              return noteNames as string
            else
              return "Folder not found: ${folder}"
            end if
          end tell
        `;
      } else {
        return `
          tell application "Notes"
            set noteNames to name of notes
            return noteNames as string
          end tell
        `;
      }
    },
  • Input schema defining optional 'folder' parameter for listing notes from a specific folder.
    schema: {
      type: "object",
      properties: {
        folder: {
          type: "string",
          description: "Optional folder name to list notes from"
        }
      }
    }
  • Registers the 'notes_list' tool by constructing the name from category 'notes' and script 'list', along with description and schema.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: this.categories.flatMap((category) =>
        category.scripts.map((script) => ({
          name: `${category.name}_${script.name}`, // Changed from dot to underscore
          description: `[${category.description}] ${script.description}`,
          inputSchema: script.schema || {
            type: "object",
            properties: {},
          },
        })),
      ),
    }));
  • src/index.ts:35-35 (registration)
    Registers the notes category containing the 'list' script, which becomes the 'notes_list' tool.
    server.addCategory(notesCategory);
Behavior2/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 of behavioral disclosure. It mentions the action ('List') but does not cover critical aspects such as whether the operation is read-only, if it requires permissions, how results are returned (e.g., pagination, format), or any rate limits. The description is too vague to adequately inform an agent about behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded in a single sentence, efficiently conveying the core functionality without unnecessary details. However, it could be slightly improved by structuring it to better highlight key usage points, such as emphasizing the optional nature of the folder parameter.

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?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It fails to address behavioral aspects like safety, return format, or error handling, and does not differentiate from sibling tools. For a list operation with no structured support, more contextual detail is needed.

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?

The description adds minimal semantic context by noting the folder parameter is optional and for listing notes from a specific folder, but the input schema already provides 100% coverage with a clear description ('Optional folder name to list notes from'). Thus, the description does not significantly enhance parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('notes'), specifying it can list all notes or notes in a specific folder. However, it does not explicitly distinguish this tool from sibling tools like 'notes_search' or 'notes_get', which might offer overlapping or alternative functionality for retrieving notes.

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 provides minimal guidance by mentioning the optional folder parameter, but it does not specify when to use this tool versus alternatives such as 'notes_search' (for filtered searches) or 'notes_get' (for retrieving a specific note). No explicit when-not-to-use or prerequisite information is included.

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/joshrutkowski/applescript-mcp'

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