Skip to main content
Glama

notes_create_note

Create new notes with title and content on macOS, organizing them into folders for efficient information management.

Instructions

Create new note with title and content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNote title
contentYesNote content/body
folderNoTarget folder name (optional, defaults to "Notes")

Implementation Reference

  • The handler case for 'notes_create_note' that validates input parameters (title, content, optional folder), constructs and executes an osascript AppleScript command to create a new note in the specified Notes folder, and returns success or error message.
    case 'notes_create_note':
      try {
        const title = (args?.title as string) || '';
        const content = (args?.content as string) || '';
        const folder = (args?.folder as string) || 'Notes';
        
        if (!title || !content) {
          return {
            content: [
              {
                type: 'text',
                text: 'Error: title and content are required',
              },
            ],
          };
        }
        
        const command = `osascript -e 'on run argv
          set noteTitle to item 1 of argv
          set noteContent to item 2 of argv
          set targetFolderName to item 3 of argv
    
          tell application "Notes"
            set targetFolder to folder targetFolderName
            set newNote to make new note in targetFolder with properties {name:noteTitle, body:noteContent}
            return "Note created: " & name of newNote & " in folder: " & name of targetFolder
          end tell
        end run' -- "${title}" "${content}" "${folder}"`;
        
        const { stdout, stderr } = await execAsync(command);
        
        if (stderr.trim()) {
          return {
            content: [
              {
                type: 'text',
                text: `Error creating note: ${stderr.trim()}`,
              },
            ],
          };
        }
        
        return {
          content: [
            {
              type: 'text',
              text: stdout.trim(),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Error executing note creation command: ${error.message}`,
            },
          ],
        };
      }
  • src/index.ts:176-196 (registration)
    Registration of the 'notes_create_note' tool in the ListTools response, including name, description, and input schema definition.
    {
      name: 'notes_create_note',
      description: 'Create new note with title and content',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Note title',
          },
          content: {
            type: 'string',
            description: 'Note content/body',
          },
          folder: {
            type: 'string',
            description: 'Target folder name (optional, defaults to "Notes")',
          },
        },
        required: ['title', 'content'],
      },
  • Input schema for the notes_create_note tool defining parameters title (required string), content (required string), and optional folder (string).
    inputSchema: {
      type: 'object',
      properties: {
        title: {
          type: 'string',
          description: 'Note title',
        },
        content: {
          type: 'string',
          description: 'Note content/body',
        },
        folder: {
          type: 'string',
          description: 'Target folder name (optional, defaults to "Notes")',
        },
      },
      required: ['title', 'content'],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Create new note' which implies a write/mutation operation, but doesn't mention permissions needed, whether creation is immediate or requires confirmation, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is insufficient.

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 extremely concise at just 6 words, with zero wasted language. It's front-loaded with the core action ('Create new note') and specifies key parameters. Every word earns its place, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after creation (e.g., returns note ID, opens the note, etc.), error conditions, or behavioral constraints. Given the complexity of a write operation and lack of structured coverage, more context 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?

Schema description coverage is 100%, so the schema already documents all three parameters (title, content, folder) with their types and descriptions. The description mentions 'title and content' which aligns with required parameters but adds no additional semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Create') and resource ('new note'), specifying what the tool does. It distinguishes from siblings like notes_get_recent_notes (read) and notes_search_notes (search), but doesn't explicitly differentiate from other creation tools like calendar_create_event or reminders_create_reminder beyond the resource type.

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 on when to use this tool versus alternatives is provided. It doesn't mention prerequisites, when-not-to-use scenarios, or compare with similar creation tools like textedit_create_document or mail_create_message. The description only states what it does, not when to choose 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/samicokar/mcp-mac'

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