Skip to main content
Glama

feishu_drive_file

Manage files in Feishu Drive by listing, copying, moving, deleting, uploading, or downloading documents, sheets, and other file types.

Instructions

【以用户身份】飞书云空间文件管理工具。当用户要求查看云空间(云盘)中的文件列表、获取文件信息、复制/移动/删除文件、上传/下载文件时使用。消息中的文件读写禁止使用该工具!

Actions:

  • list(列出文件):列出文件夹下的文件。不提供 folder_token 时获取根目录清单

  • get_meta(批量获取元数据):批量查询文档元信息,使用 request_docs 数组参数,格式:[{doc_token: '...', doc_type: 'sheet'}]

  • copy(复制文件):复制文件到指定位置

  • move(移动文件):移动文件到指定文件夹

  • delete(删除文件):删除文件

  • upload(上传文件):上传本地文件到云空间。提供 file_path(本地文件路径)或 file_content_base64(Base64 编码)

  • download(下载文件):下载文件到本地。提供 output_path(本地保存路径)则保存到本地,否则返回 Base64 编码

【重要】copy/move/delete 操作需要 file_token 和 type 参数。get_meta 使用 request_docs 数组参数。 【重要】upload 优先使用 file_path(自动读取文件、提取文件名和大小),也支持 file_content_base64(需手动提供 file_name 和 size)。 【重要】download 提供 output_path 时保存到本地(可以是文件路径或文件夹路径+file_name),不提供则返回 Base64。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
folder_tokenNo文件夹 token(可选)。不填写或填空字符串时,获取用户云空间根目录下的清单(注意:根目录模式不支持分页和返回快捷方式)
page_sizeNo分页大小(默认 200,最大 200)
page_tokenNo分页标记。首次请求无需填写
order_byNo排序方式:EditedTime(编辑时间)、CreatedTime(创建时间)
directionNo排序方向:ASC(升序)、DESC(降序)
request_docsNo要查询的文档列表(批量查询,最多 50 个)。示例:[{doc_token: 'Z1FjxxxxxxxxxxxxxxxxxxxtnAc', doc_type: 'sheet'}]
file_tokenNo文件 token(必填)
nameNo目标文件名(必填)
typeNo文档类型(必填)
parent_nodeNo【folder_token 的别名】目标文件夹 token(为兼容性保留,建议使用 folder_token)
file_pathNo本地文件路径(与 file_content_base64 二选一)。优先使用此参数,会自动读取文件内容、计算大小、提取文件名。
file_content_base64No文件内容的 Base64 编码(与 file_path 二选一)。当不提供 file_path 时使用。
file_nameNo文件名(可选)。如果提供了 file_path,会自动从路径中提取文件名;如果使用 file_content_base64,则必须提供此参数。
sizeNo文件大小(字节,可选)。如果提供了 file_path,会自动计算;如果使用 file_content_base64,则必须提供此参数。
output_pathNo本地保存的完整文件路径(可选)。必须包含文件名和扩展名,例如 '/tmp/file.pdf'。如果不提供,则返回 Base64 编码的文件内容。
Behavior4/5

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

With no annotations provided, the description carries full burden and does well: it discloses behavioral traits like authentication context ('以用户身份'), file handling specifics (e.g., upload prioritizes file_path, download returns Base64 if no output_path), and important constraints (e.g., copy/move/delete need file_token and type). It doesn't mention rate limits or error behaviors, but covers key operational details.

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 well-structured with a purpose statement, usage guidelines, action list, and important notes. It's appropriately sized for a multi-action tool (16 parameters), though some sentences could be more front-loaded (e.g., the action list is detailed but necessary). There's minimal waste, but the Chinese/English mix and bullet points slightly affect flow.

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?

Given the tool's complexity (multi-action, 16 parameters, no annotations, no output schema), the description is largely complete: it covers purpose, usage, actions, and key parameter semantics. However, it lacks details on return values (e.g., what list returns) and error handling, which would help compensate for the missing output schema. It's sufficient but not exhaustive.

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 description coverage is high (94%), so the baseline is 3. The description adds value by clarifying parameter usage beyond the schema: e.g., it explains that folder_token is optional for list actions (root directory if not provided), specifies format examples for request_docs, and details the interplay between file_path/file_content_base64 and file_name/size for upload. This compensates for the minor schema gaps.

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 clearly states the tool's purpose as '飞书云空间文件管理工具' (Feishu cloud space file management tool) and lists specific actions (list, get_meta, copy, move, delete, upload, download) with their functions. It distinguishes from siblings by explicitly stating when NOT to use it ('消息中的文件读写**禁止**使用该工具!'), making the purpose specific and differentiated.

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

Usage Guidelines5/5

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

The description provides explicit usage guidelines: it states when to use ('当用户要求查看云空间(云盘)中的文件列表、获取文件信息、复制/移动/删除文件、上传/下载文件时使用') and when NOT to use ('消息中的文件读写**禁止**使用该工具!'). It also implicitly guides usage among its own actions by describing each action's purpose, though it doesn't name external alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WilliamMo101/lark-hermes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server