mcp-pcloud-crunchtools

Pcloud List Folder

pcloud_list_folder

Read-only

List contents of a pCloud folder with file and folder metadata. Optionally recurse into subfolders to browse the full directory structure.

Instructions

List contents of a folder in pCloud with file and folder metadata.

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

Input Schema

Name	Required	Description	Default
`path`	Yes
`recursive`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.1Oct 17, 2026
- removedInput schema / properties / path / default
```
Removed value: -"/"
```
- addedInput schema / required
```
Added value: +[
+  "path"
+]
```
Changed2 schema fields changedv2.5.0Sep 22, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
First observedv2.1.0Sep 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read, so the bar is lower. The description only adds that results carry file and folder metadata; it says nothing about behavior for nonexistent paths, very large folders, or pagination.

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?

A single front-loaded sentence with no filler. Every word contributes to identifying the operation and its payload.

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?

An output schema exists, so return structure need not be explained, and annotations cover the safety profile. However, for a listing tool with a recursive flag, the description should state what recursion does and how large or deep results are handled.

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%, so both parameters are undocumented in the schema. The description implies that "path" is a folder path, but it says nothing about the "recursive" flag — the single most consequential behavioral parameter, silently defaulting to false. The description does not compensate for the coverage gap.

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 and resource ("List contents of a folder in pCloud") and adds what the response contains (file and folder metadata). It is unambiguous on its own, but it does not distinguish itself from or reference any sibling such as pcloud_search or pcloud_get_file_info.

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 tool versus alternatives like pcloud_search (which would be the choice for locating a file by name) or pcloud_get_file_info (single-item metadata). No prerequisites or when-not-to-use conditions are offered.

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

Deploy Server