feishu-user-plugin

manage_drive_file

Copy, move, or delete Feishu Drive files and folders. Provide file token, resource type, and action; optionally specify destination folder or new name.

Instructions

[Official API] Manage a Drive file/doc/folder. action=copy (duplicate to a new name + folder), move (relocate, returns task_id), delete (remove, returns task_id). type is always required (Feishu rejects with 1061002 / 1062501 otherwise).

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": {
      "action": "<action>",
      "file_token": "<file_token>",
      "type": "<type>"
    },
    "name": "manage_drive_file"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Operation to perform
`file_token`	Yes	File/folder token to operate on (required for all actions).
`type`	Yes	Resource type — Feishu requires this to know which API table to look up.
`name`	No	New name — required for action=copy.
`folder_token`	No	Destination folder token — required for action=move; optional for action=copy (defaults to root).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.10May 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that move and delete return task_id, and that type is always required with specific Feishu error codes (1061002/1062501). However, it does not state whether delete is permanent or whether special permissions are needed.

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?

The description is a single sentence that front-loads the purpose and action list. It is compact, but the dense action list may require careful reading. Every clause adds value.

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 has three distinct actions and five parameters with no output schema. The description covers the actions and mentions task_id returns for move/delete, but does not specify copy's return value or any constraints like required permissions. Some behavioral gaps remain for a tool of this complexity.

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?

Schema coverage is 100%, so baseline is 3. The description adds context that name is needed for copy and that type is always required, but the schema already specifies these. The error codes are useful but not parameter-specific semantics.

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 names the resource (Drive file/doc/folder), the verb (manage), and enumerates the specific actions (copy, move, delete) with their effects, clearly distinguishing this from sibling tools that upload or create resources.

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 copy/move/delete operations but does not explicitly state when this tool should be preferred over alternatives like upload_file or create_folder. No exclusions or alternative tool mentions are present.

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

Deploy Server