Skip to main content
Glama

新增多维表格记录

feishu_bitable_add

Adds a single record to a Feishu Bitable table and returns its record_id for later updates. Use it to save conversation conclusions, to-dos, or collected data into a table with field values matching each field type.

Instructions

往某个数据表里新增一条记录,返回 record_id(后续更新要用)。这是写操作,会真的改用户的表:不确定字段名和类型时,先调 feishu_bitable_fields 看定义、feishu_bitable_records 看现有数据的写法,别凭猜写。fields 的 key 必须是字段名(不是 field_id),值形态要匹配字段类型:文本传字符串、数字传数字、日期传毫秒时间戳、单选传选项字符串、多选/人员/附件/关联传数组。适合:把对话里的结论、待办、采集到的数据落进表。不适合:批量导入几百条(逐条调用会很慢)。

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

Input Schema

NameRequiredDescriptionDefault
fieldsYes字段名 → 值。key 用字段名(不是 field_id),值形态必须匹配字段类型:文本传字符串("张三")、数字传数字(42)、日期传毫秒时间戳(1700000000000)、单选传选项字符串("进行中")、多选传字符串数组(["A","B"])、人员传 [{"id":"ou_xxx"}]、附件传 [{"file_token":"box_xxx"}]、复选框传 true/false。只写想设值的字段,没写的字段保持空。
table_idYes要写入的数据表 id(形如 tbliz1PrMZkp1DSN)
app_tokenYes多维表格的 app_token(Base 链接里 /base/ 后面那串)

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 only give readOnlyHint=false and openWorldHint=true; the description adds that this really mutates the user's table, advises verification of field definitions first, and warns about per-record slowness for bulk imports. It does not cover write-result details beyond record_id or failure modes, but the mutation warning is substantial added value.

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-loads what it does and the returned record_id, then the write warning, then usage fit. The type-mapping sentence duplicates the schema but keeps the definition self-contained; slight redundancy keeps it from a 5.

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 3-param write tool with no output schema, it covers purpose, return value, mutation risk, prerequisite lookups, and usage boundaries. Missing only edge-case behavior such as permission errors or partial-write outcomes.

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% and the fields description already documents key=field name and per-type value shapes in more detail than the description. The description repeats this rule (key 必须是字段名, not field_id) and lists type mappings, adding little beyond 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+resource (新增一条记录 into a 数据表) and names the return value (record_id). Clearly distinguishable from sibling feishu_bitable_update/delete/records.

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?

Explicit when-to-use (把对话结论/待办/采集数据落进表) and when-not-to-use (批量导入几百条, 逐条调用慢), plus routing advice to feishu_bitable_fields and feishu_bitable_records before guessing field names/types.

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