Skip to main content
Glama

列云空间文件

feishu_drive_list
Read-only

List files and subfolders in a Feishu Drive folder and return type, name, token, and modified time. Use each token to read its document or inspect its bitable tables; omit folder token for root.

Instructions

列出云空间(我的空间)里某个文件夹下的文件,返回类型、名字、token、修改时间。使用场景:模型只知道"有个文档/表格",需要先找到它的 token 时;或者要盘点某个目录里都有什么。folder_token 不填等于根目录。返回的 token 就是下一步要用的钥匙:docx 类型的 token 传给 feishu_doc_read 读正文;bitable 类型的 token 传给 feishu_bitable_tables 看表结构。前置条件:应用需要有云空间读取权限(drive:drive 或 drive:drive.metadata:readonly),且目标文件夹已共享给该应用。只读操作,不会修改云空间任何内容。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "feishu_drive_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo最多返回多少个条目,默认 50,上限 200(超过按上限处理)。
folder_tokenNo要列出的文件夹 token;不填或传空字符串表示根目录。子文件夹的 token 来自上一层的返回。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description goes further by naming required permission scopes (drive:drive or drive:drive.metadata:readonly) and the precondition that the folder must be shared with the app — real invocation blockers an agent otherwise could not anticipate. It also describes the return payload shape, though it repeats read-only and the limit/default behavior that the schema already states, so it is not exhaustive.

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?

Purpose is front-loaded, followed by use cases, token routing, prerequisites, and a safety note — a logical order with no filler sentences. It is somewhat dense and repeats the read-only/limit points already carried by annotations and schema, costing a bit of tightness.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the returned fields and explaining what each token type is used for. Combined with permission prerequisites and the root-folder default, an agent has everything needed to call this tool correctly on the first attempt.

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 both parameters are already documented. The description restates the root-folder default and adds provenance for folder_token (subfolder tokens come from a prior listing result), which is mildly useful but largely duplicative of the schema text.

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?

States a specific verb and resource (列出云空间某个文件夹下的文件) and enumerates the returned fields (类型、名字、token、修改时间). It also distinguishes itself from downstream siblings by naming which tool consumes each token type (feishu_doc_read for docx, feishu_bitable_tables for bitable), so an agent can position it precisely in the workflow.

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?

Provides explicit scenarios: when the model only knows a document/sheet exists and needs its token, or when inventorying a directory. The downstream routing rule (which token goes to which tool) gives actionable next-step guidance rather than vague context, leaving little to inference.

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