Skip to main content
Glama
henilcalagiya

io.github.henilcalagiya/mcp-apple-notes

move_folder

Moves an Apple Notes folder to a new location using its ID, with AppleScript verification and duplicate name prevention.

Instructions

Move a folder from one location to another in Apple Notes by ID with AppleScript verification.

Features:

  • Moves folders by ID with AppleScript verification

  • Comprehensive validation and duplicate detection

  • Unicode and emoji support for folder names

  • Works with root level and nested paths

Validation:

  • Validates target path exists

  • Prevents duplicate names in target location

  • Enforces 5-level nesting depth limit

  • AppleScript verifies ID and name match the same folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesPrimary key ID of the folder to move (e.g., 'p2330')
folder_nameYesName of the folder to verify and move
target_pathNoTarget path where to move the folder (e.g., 'Archive'). If empty, moves to root level.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Given no annotations, the description fully discloses behavioral traits including AppleScript verification, validation, duplicate detection, Unicode support, and nesting depth limit.

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?

Well-structured with headings and bullet points, front-loaded main action. Slight redundancy between features and validation lists.

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

Completeness5/5

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

Covers purpose, features, validation rules, and compatibility details. Output schema handles return values, so no gaps.

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%, so baseline is 3. Description adds verification context but does not significantly enhance parameter understanding beyond 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 moves a folder by ID with AppleScript verification, distinguishing it from sibling tools like rename_folder or move_note.

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?

Provides clear context for moving folders with specific features, but lacks explicit when-not-to-use or alternative comparisons.

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/henilcalagiya/mcp-apple-notes'

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