Skip to main content
Glama

更新多维表格记录

feishu_bitable_update

Update specific fields of a single Feishu Bitable record by record_id, leaving all other fields unchanged. Use it to fix incorrect values, advance a status, or attach files to one record.

Instructions

按 record_id 更新某条记录的部分字段(只覆盖 fields 里出现的字段,其余字段不动)。写操作,会真的改用户的表:record_id 必须先通过 feishu_bitable_records 查到,别自己编。值形态的规矩和 feishu_bitable_add 一样:文本传字符串、数字传数字、日期传毫秒时间戳、单选传选项字符串、多选/人员/附件/关联传数组。适合:修正一条错数据、推进状态、补填附件。不适合:整表批量改(逐条调用)。

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>",
      "fields": "<fields>"
    },
    "name": "feishu_bitable_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes要改的字段名 → 新值;未出现的字段保持原值。形如 {"状态":"已完成","完成日期":1700000000000}。值形态必须匹配字段类型(文本字符串、数字数字、日期毫秒时间戳、单选选项字符串、多选/人员/附件数组)。
table_idYes记录所在的数据表 id(形如 tbliz1PrMZkp1DSN)
app_tokenYes多维表格的 app_token(Base 链接里 /base/ 后面那串)
record_idYes要更新的记录 id(rec 开头,形如 recxxxxxxxx)。先用 feishu_bitable_records 查出来。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write nature is known; the description still adds value by spelling out the partial-update semantics (untouched fields stay intact) and flagging that the write lands on the user's real table. It does not cover permission requirements or failure/partial-failure behavior, which keeps it below a 5.

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 the core behavior, then constraints, then 适合/不适合 in a scannable pattern; every segment carries information. It loses a point only because the type-mapping sentence repeats what the fields schema already documents.

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?

For a 4-required-parameter mutation with a nested fields object and no output schema, the description covers the mutation risk, the patch contract, value typing, and the ID provenance requirement. It does not say what a successful call returns (echoed record vs. bare success), which is the remaining gap an agent would want closed.

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 description coverage is 100% and the value-shape rules (text as string, date as ms timestamp, arrays for multi-select/person/attachment/link) are already stated in the fields property description, so the description largely restates structured data. The record_id lookup warning is likewise duplicated from the schema, leaving no genuinely new parameter meaning beyond the baseline.

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 (按 record_id 更新某条记录) and immediately narrows scope with the patch semantic '只覆盖 fields 里出现的字段,其余字段不动'. This distinguishes it from feishu_bitable_add (create) and from table-wide operations without the agent needing to open any schema.

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 prerequisite (record_id 必须先通过 feishu_bitable_records 查到,别自己编), explicit positive cases (修正一条错数据、推进状态、补填附件) and an explicit exclusion with the alternative pattern (不适合整表批量改,逐条调用). When-to-use, when-not-to-use, and the sibling to consult are all present.

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