Skip to main content
Glama

数据表的字段定义

feishu_bitable_fields
Read-only

Lists every field in a Feishu Bitable table—names, IDs, type codes, and required JSON value formats—so you can build valid add/update payloads before writing records.

Instructions

列出某个数据表的全部字段:字段名、field_id、类型码 + 中文类型名,以及这个字段写入时该传的值形态。新增/更新记录之前先调这个:飞书不同字段类型吃的 JSON 形态完全不同(文本传字符串、日期传毫秒时间戳、人员传 [{"id":"ou_xxx"}]、附件传 [{"file_token":"box_xxx"}]),先看类型码再写 fields,能避免 1254001 / 1254045 之类的字段校验报错。字段名就是 feishu_bitable_add / feishu_bitable_update 里 fields 的 key,必须一字不差。只返回文本,不修改数据。

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

Input Schema

NameRequiredDescriptionDefault
table_idYes数据表 id(形如 tbliz1PrMZkp1DSN)。不知道就先调 feishu_bitable_tables。
app_tokenYes多维表格的 app_token(Base 链接里 /base/ 后面那串)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation it discloses that the call returns text only, mutates nothing, and exists to preempt specific validation failures (1254001 / 1254045). It also warns that field names must match exactly when used as fields keys. It stops short of describing format details such as ordering or pagination, which keeps it at 4 rather than 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 return payload, then the when-to-use rule, then the rationale with concrete JSON examples. The parenthetical type examples are long but each earns its place by showing why the call matters. A single dense block rather than clearly separated structure costs it one point.

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?

There is no output schema, and the description compensates by naming every returned column and the per-type value shapes an agent must write back. Combined with the explicit linkage to the add/update tools' fields key, nothing needed to invoke or use the result 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?

Schema coverage is 100%, so app_token and table_id are already fully documented in the schema, including the /base/ URL hint and the tbl... format. The description body adds nothing about the parameters themselves. Baseline 3 applies when the schema carries the parameter burden.

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 enumerates exactly what is returned: field name, field_id, type code plus Chinese type name, and the JSON shape expected for writes. The closing line 只返回文本,不修改数据 separates it cleanly from the mutating siblings feishu_bitable_add / feishu_bitable_update.

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?

Explicitly prescribes when to call it: 新增/更新记录之前先调这个, and names the tools it precedes (feishu_bitable_add, feishu_bitable_update). The schema further routes users who lack a table_id to feishu_bitable_tables, so the when-to-use and prerequisite paths are both covered.

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