mcp-pcloud-crunchtools

Pcloud Get File Link

pcloud_get_file_link

Read-only

Create a temporary direct download URL for a pCloud file by path, enabling sharing or retrieval without a permanent link.

Instructions

Get a temporary direct download URL for a file 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>"
    },
    "name": "pcloud_get_file_link"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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?

Annotations already declare readOnlyHint=true, so safety is covered. The description does add one genuine behavioral trait beyond the annotations — the URL is 'temporary' — but does not say how long it lasts or whether it requires auth. Modest added value over structured data.

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; the key result type ('temporary direct download URL') is stated immediately.

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 values need not be explained, and the read-only annotation covers safety. However, the description omits link lifetime and path format, which an agent needs to use the tool correctly.

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% and there is one required parameter, so the description carries the burden of explaining what 'path' means. It only implies a file path via 'a file in pCloud' and adds no format, root-prefix, or relative/absolute guidance, leaving the single parameter under-specified.

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?

States a specific verb ('Get') and resource ('a temporary direct download URL for a file in pCloud'), which distinguishes it from folder-oriented siblings and from auth/info tools. It does not explicitly contrast with the closest sibling, pcloud_create_public_link, so a 4 rather than 5.

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?

No guidance on when to use this versus pcloud_create_public_link (permanent public link) or pcloud_get_file_info. The intent is inferable from the name, but the description offers no context, prerequisites, or alternatives.

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

Deploy Server