icloud-mcp

icloud_move

Move a file or folder into another folder in iCloud Drive, updating iCloud directly so changes appear on all devices.

Instructions

Move a file or folder into another folder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "dest_folder": "<dest_folder>"
    },
    "name": "icloud_move"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`dest_folder`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

C2.7/5.0

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 behavioral burden, yet it discloses nothing about whether the destination folder must already exist, whether an existing file at the destination is overwritten, whether the move is atomic or reversible, or what happens across folders. 'Into another folder' is the only behavioral constraint offered.

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?

A single, front-loaded sentence with no filler, which is appropriately sized for the operation. It is efficient but so terse that it leaves no room for the guidance a mutation tool needs.

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?

An output schema exists, so return values need not be explained, but for a two-parameter mutation tool with no annotations and no parameter documentation the description is too thin. An agent cannot determine from it whether the destination must pre-exist or what failure/overwrite semantics apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, and the description does not compensate: it never explains whether 'path' is relative or absolute, or whether 'dest_folder' must be an existing directory. The phrase 'a file or folder' for path and 'another folder' for dest_folder merely restates the schema property titles ('Path', 'Dest Folder').

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 states a specific verb (Move) and resource (a file or folder) with the destination scope ('into another folder'). It is clear on its own, but it does not distinguish itself from the close sibling icloud_rename, which is the operation an agent is most likely to confuse with a move.

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?

There is no guidance on when to use this versus icloud_rename, icloud_upload, or icloud_mkdir, and no prerequisites or exclusions are given. The agent must infer the use case purely from the one-line purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server