pcloud_list_folderList folder contents in pCloud, retrieving file and folder metadata with optional recursive scanning.
List contents of a folder in pCloud with file and folder metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | / | |
| recursive | No |
| 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 provided, so the description must disclose behavioral traits. It only states the basic action with no details on pagination, sorting, recursion effects, or potential side effects. For a read-only tool this is acceptable but still sparse; it does not add context beyond the immediate action.
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 concise sentence with no wasted words. It is front-loaded with the verb and resource, making it easy to parse, though it is arguably too terse to be fully self-contained.
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?
With an output schema present, return format details are covered, but the description fails to explain parameter behavior (recursive, path default) and offers no usage context. The tool has only two optional parameters, yet the description leaves them completely unexplained, making the definition incomplete for an agent.
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 schema has 0% description coverage, and the description does not explain the path parameter (default '/') or the recursive flag. The agent receives no additional meaning about parameter formats, defaults, or effects beyond the raw schema properties.
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 clearly states the action (list contents), the resource (folder in pCloud), and the result (file and folder metadata). It differentiates from sibling tools like pcloud_create_folder or pcloud_delete_folder by focusing on reading, and is specific enough for an agent to select it.
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?
The description provides no guidance on when to use this tool versus alternatives like pcloud_search or pcloud_get_file_info. It does not mention prerequisites, exclusions, or typical use cases, leaving the agent to infer the obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.