Skip to main content
Glama

删除多维表格记录

feishu_bitable_delete
Destructive

Deletes one Feishu Bitable record by record_id and requires explicit confirmation because the deletion is irreversible; use update instead to change a record's status.

Instructions

按 record_id 删掉一条记录。不可撤销:删了就没了,没有回收站。record_id 必须先通过 feishu_bitable_records 查到,别自己编。一次只能删一条,要删多条就多次调用。如果用户只是想改状态(比如改成「已完成」),用 feishu_bitable_update,别删。

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": {
      "app_token": "<app_token>",
      "table_id": "<table_id>",
      "record_id": "<record_id>",
      "confirm": "<confirm>"
    },
    "name": "feishu_bitable_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes必须传 true 表示确认删除。这是防手滑:删记录不可恢复。
table_idYes记录所在的数据表 id(形如 tbliz1PrMZkp1DSN)
app_tokenYes多维表格的 app_token(Base 链接里 /base/ 后面那串)
record_idYes要删除的记录 id(rec 开头)。先用 feishu_bitable_records 查出来,别猜。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the details they cannot express: the deletion is irreversible, there is no recycle bin, and only one record can be removed per call. That is exactly the extra context an agent needs before performing a destructive operation.

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 action, immediately follows with the irreversibility warning, then the prerequisite and the alternative; every sentence carries a distinct instruction. No filler or repetition of the schema.

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 four-parameter destructive tool with no output schema, the definition covers the risk profile, the record_id provenance, the single-record limit, and the correct alternative tool. Nothing an agent needs in order to invoke it safely 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 description coverage is 100%, and each parameter already documents its own format, including the confirm guard. The description still adds value by telling the agent where record_id must come from rather than inventing one, though it does not restate the confirm flag or the app_token/table_id formats.

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 plus the scoping key: delete one record by record_id. It also draws the contrast with feishu_bitable_update (editing status) and with feishu_bitable_records (lookup), so an agent can distinguish it from the nearest siblings without reading their schemas.

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 rules and a when-not-to-use rule: fetch record_id from feishu_bitable_records first, one deletion per call, and use feishu_bitable_update if the user only intends to change a status field. The prerequisite and the alternative are both named, so no inference is required.

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