pcloud_copy_folderCopy a pCloud folder to a new destination path by providing the source folder and target location, duplicating the folder and its contents in cloud storage.
Copy a folder in pCloud to a new location.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| to_path | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v2.5.0Input schema / additionalPropertiesAdded value: +falseOutput schema / descriptionRemoved value: -"Generic wrapper for non-object return types."v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It states that a folder is copied, but does not explain behavior such as whether the copy is recursive, what happens if the destination already exists, or whether the original is preserved. This is minimal disclosure for a tool that could have important edge cases.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no redundant wording. It immediately states the operation and result, earning its place without filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple operation and the presence of an output schema, a short description is partly justified; return values do not need explanation. However, the description lacks parameter semantics and edge-case behavior, and with no annotations the tool definition is only minimally viable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides no descriptions for 'path' or 'to_path', and schema description coverage is 0%. The description only implies that one path is the source and the other is the destination; it does not explain path format, folder-only constraints, or whether destination parent folders need to exist. The description does not compensate for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Copy') and resource ('folder') and clearly states the outcome: moving it to a new location. This distinguishes it from sibling tools like pcloud_copy_file, pcloud_delete_folder, and pcloud_rename_folder.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives. It does not mention that it is the appropriate choice for folders rather than files, nor does it provide any conditions, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.