Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Update a transfer

update_transfer
Idempotent

Change a live transfer's title, message, expiry, or download password without re-uploading files. Update only specified fields; clear title/message or remove password as needed.

Instructions

Change a live transfer: title, message, expiry (later only, Pro/Team, at most 90 days after it was sent – get_transfer shows latest_possible_expiry) and the download password (set a new one, or remove it with remove_password). Only the fields you give change.

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": {
      "id": "<id>"
    },
    "name": "update_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTransfer id: the last part of the share link (https://pandafile.co/d/<id>), e.g. "k3x9q2m7ab".
titleNoNew title (null clears it).
messageNoNew message (null clears it).
passwordNoDownload password (8–200 characters). Recipients need it to download. Plus/Pro/Team only.
expires_atNoExact expiry as ISO 8601 (e.g. "2026-12-31T23:00:00Z"). Alternative to expires_in_days; same limits.
expires_in_daysNoKeep the files this many days from now (1–90). Pro/Team only, at most 90 days after sending; not for test keys. Leave out for the plan default.
remove_passwordNotrue removes the download password.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this a non-destructive, idempotent write, and the description adds real value on top: partial-update semantics ("Only the fields you give change"), plan gating, and expiry-window limits. It stops short of saying what happens when the transfer is already expired or closed, or what errors to expect, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence opens with the verb and resource, then packs constraints into a parenthetical that earns its space. It is dense but not padded; splitting the expiry rules into a separate sentence would improve scanability slightly.

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

Completeness4/5

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

With 7 parameters, one required, no output schema and full annotation coverage, the description covers the mutation contract, plan restrictions and expiry bounds. Only edge-case behavior (expired or closed transfers, failure modes) is left implicit, which is acceptable here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by pointing to get_transfer for the latest permissible expiry and clarifying that the password can either be replaced or removed via remove_password. It does not disambiguate expires_at versus expires_in_days, leaving that to the schema.

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?

"Change a live transfer" states a specific verb and resource, then enumerates exactly which fields are mutable (title, message, expiry, download password). Naming get_transfer as the place to look up latest_possible_expiry further separates it from a read-only sibling.

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

Usage Guidelines4/5

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

The description gives concrete conditions for the expiry fields (later only, Pro/Team, at most 90 days after it was sent, check get_transfer for the latest possible date) and explains how to clear a password. It does not explicitly contrast against alternatives such as delete_transfer or add_recipients, but the context is clear enough to act on.

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