Skip to main content
Glama

新建电子表格

feishu_sheet_create

Creates a new empty Feishu spreadsheet in the cloud workspace and returns its spreadsheet_token and shareable link, optionally inside a specified folder. Use it when starting a sheet from scratch, not for writing to an existing one.

Instructions

在飞书云空间里新建一张空的电子表格(Sheets),返回 spreadsheet_token 与可分享的链接。写操作,会在用户的云文档里真的建一个文件。适合:用户要"建个表记录一下"这类从零开始的场景。不适合:已经有表格只是要写数据(应该拿现有 spreadsheet_token 去读写,而不是新建)。folder_token 不填就建在"我的空间"根目录;要建进某个文件夹,先用云空间相关工具拿到文件夹 token。建完可以接着用 feishu_send_text 把链接发给用户。

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_sheet_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes电子表格文件名(用户看到的名字),如 "2026 Q1 周报汇总"。不用带 .xlsx 后缀。
folder_tokenNo目标文件夹 token(形如 fldcnxxxx)。不填则建在云空间"我的空间"根目录。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the meaningful consequence that a real file is created in the user's cloud docs, plus the default landing location when folder_token is omitted. It stops short of covering permissions or quota behavior, but the key side effect is disclosed.

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

Conciseness5/5

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

Front-loads the core action and return values, then routes to usage conditions and parameters. No redundant or filler sentences; each clause carries decision-relevant information.

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 2-parameter create tool with no output schema, the description covers what is created, what is returned, where it is created, when to prefer an alternative, and what to do afterward. Nothing needed for correct invocation is missing.

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 already 100%, so the baseline is 3; the description still adds value by explaining how to obtain a folder token via the drive tools and reiterating the root 'my space' default. Title semantics (user-visible name, no .xlsx suffix) largely duplicate 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?

States a specific verb and resource ('在飞书云空间里新建一张空的电子表格'), and explicitly names the return artifacts (spreadsheet_token, shareable link). It distinguishes itself from sibling write/read tools by specifying this creates an empty sheet from scratch rather than writing into an existing one.

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 explicit when-to-use ('建个表记录一下' from-scratch scenarios) and when-not-to-use ('已经有表格只是要写数据' should reuse the existing spreadsheet_token). It also supplies the prerequisite flow for folder_token and a follow-up step with feishu_send_text.

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