Skip to main content
Glama

新建飞书文档

feishu_doc_create

Creates an empty Feishu docx document in a chosen cloud folder and returns its document_id, so agents can store results in a shareable file for later reading or editing.

Instructions

在云空间里新建一个空的 docx 文档,返回 document_id,后续可用 feishu_doc_read 读回校验。使用场景:需要把结果沉淀成一份飞书文档、并且希望它在云空间里可被同事打开时。只建空文档,不写正文内容;需要正文请建完后再用其它编辑能力写。前置条件(重要):当前应用缺 docx:document:create,调用大概率返回 99991672。真失败了不要重试、也不要换参数硬试,去开放平台开通 docx:document:create 并重新发布版本。folder_token 不填等于建在应用自己的根目录(通常同事看不到,建议显式给一个已共享的文件夹)。

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": {
      "title": "<title>"
    },
    "name": "feishu_doc_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes新文档标题(就是云空间里显示的文件名)。
folder_tokenNo建在哪个文件夹下;不填则建在应用根目录。token 可从 feishu_drive_list 的 folder 条目拿。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is not read-only and reaches outside; the description adds substantially more: the permission prerequisite, the likely error code, the remediation step (enable scope and republish the version), and the visibility consequence of the default folder. It also discloses the return value (document_id) that annotations do not mention.

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?

Front-loaded with purpose, then usage scenario, then scope boundary, then prerequisites, with no filler sentences. The permission caveat is long and uses emphatic formatting, so it is slightly heavier than a pure tool definition needs, but each sentence carries operational value.

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?

For a two-parameter mutation tool with no output schema, it covers what an agent needs: return value, default-behavior risk, permission failure mode, and the boundary against follow-up editing tools. Nothing material is missing.

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?

With 100% schema coverage, the schema already documents both parameters, so the baseline is a 3. The description does add value by explaining what the folder_token default means in practice (app root, usually invisible to colleagues, so supply a shared folder) and where to obtain the token (feishu_drive_list folder entries).

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: creates an empty docx in the cloud space and returns document_id. It explicitly bounds scope ("只建空文档,不写正文内容") and points to siblings for writing body content, so an agent can distinguish it from feishu_doc_append/feishu_doc_blocks and from feishu_doc_read.

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?

Gives an explicit when-to-use scenario (persisting results as a Feishu doc that colleagues can open) and a when-not-to (it creates an empty doc only; use other editing capabilities afterwards). It also documents a hard prerequisite (the docx:document:create scope) plus the exact failure code 99991672 and tells the agent not to retry or vary parameters, which is actionable routing guidance.

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