mcp-pcloud

pcloud_rename_folder

Rename or move a folder in pCloud using its current path and a new path.

Instructions

Rename or move a folder in pCloud.

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>",
      "newPath": "<newPath>"
    },
    "name": "pcloud_rename_folder"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Current path of the folder
`newPath`	Yes	New path/name for the folder

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It merely says 'rename or move' without detailing side effects, safety profile, or potential errors (e.g., whether the operation can overwrite existing folders or requires authentication). This is insufficient for a mutation tool.

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 a single concise sentence that is front-loaded and contains no redundant information. It efficiently conveys the core purpose.

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

Completeness3/5

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

The tool is simple with two well-documented parameters and no output schema. However, the description lacks usage guidance and behavioral details that could help an agent invoke it safely. It is minimally sufficient but not comprehensive.

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 schema already provides complete descriptions for both parameters (path: 'Current path of the folder'; newPath: 'New path/name for the folder'), and the tool description adds no extra meaning. With 100% schema coverage, the baseline of 3 is appropriate.

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 action (rename or move) and the resource (a folder in pCloud). It distinguishes from sibling tools by explicitly targeting folders, unlike pcloud_rename_file which is for files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for renaming or moving folders but does not explicitly mention when to use it over alternatives like pcloud_rename_file or pcloud_copy_folder. The context from sibling names suggests the use case, but no explicit guidance is provided.

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

Deploy Server