Skip to main content
Glama

feishu_bitable_app_table_record

Manage records in Feishu Bitable tables by creating, reading, updating, deleting, and searching data rows with single or batch operations.

Instructions

【以用户身份】飞书多维表格记录(行)管理工具。当用户要求创建/查询/更新/删除记录、搜索数据时使用。

Actions:

  • create(创建单条记录,使用 fields 参数)

  • batch_create(批量创建记录,使用 records 数组参数)

  • list(列出/搜索记录)

  • update(更新记录)

  • delete(删除记录)

  • batch_update(批量更新)

  • batch_delete(批量删除)

⚠️ 注意参数区别:

  • create 使用 'fields' 对象(单条)

  • batch_create 使用 'records' 数组(批量)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
app_tokenYes多维表格 token
table_idYes数据表 ID
fieldsNo记录字段(单条记录)。键为字段名,值根据字段类型而定: - 文本:string - 数字:number - 单选:string(选项名) - 多选:string[](选项名数组) - 日期:number(毫秒时间戳,如 1740441600000) - 复选框:boolean - 人员:[{id: 'ou_xxx'}] - 附件:[{file_token: 'xxx'}] ⚠️ 注意:create 只创建单条记录;批量创建请使用 batch_create
record_idNo记录 ID
recordsNo要批量创建的记录列表(最多 500 条)
record_idsNo要删除的记录 ID 列表(最多 500 条)
view_idNo视图 ID(可选,建议指定以获得更好的性能)
field_namesNo要返回的字段名列表(可选,不指定则返回所有字段)
filterNo筛选条件(必须是结构化对象)。示例:{conjunction: 'and', conditions: [{field_name: '文本', operator: 'is', value: ['测试']}]}
sortNo排序规则
automatic_fieldsNo是否返回自动字段(created_time, last_modified_time, created_by, last_modified_by),默认 false
page_sizeNo每页数量,默认 50,最大 500
page_tokenNo分页标记
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it lists the available actions and notes parameter distinctions, it doesn't disclose important behavioral traits like authentication requirements, rate limits, error handling, or what happens during deletions. For a tool with 14 parameters and multiple mutation actions, this represents significant gaps in behavioral transparency.

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

Conciseness3/5

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

The description is reasonably structured with action listings and warnings, but contains some redundancy (repeating action names that are already in the schema enum) and could be more front-loaded. The Chinese text adds localization but doesn't necessarily improve conciseness for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 14 parameters, no annotations, no output schema, and multiple mutation capabilities (create/update/delete), the description is incomplete. It lacks information about return values, error conditions, authentication requirements, and important behavioral constraints that would help an agent use this tool effectively.

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?

The schema description coverage is 93%, so the schema already documents most parameters thoroughly. The description adds minimal value beyond what's in the schema - it lists the available actions and notes the distinction between 'fields' for single create and 'records' for batch create, but doesn't provide additional semantic context for the 14 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool manages Feishu Bitable records (rows) for create/query/update/delete/search operations, providing a specific verb+resource combination. However, it doesn't explicitly distinguish this multi-action tool from its sibling tools (bitableCreateRecord, bitableListRecords, bitableUpdateRecord) that appear to handle individual operations separately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('当用户要求创建/查询/更新/删除记录、搜索数据时使用'), which covers the main use cases. It doesn't explicitly state when NOT to use it or mention alternatives among the sibling tools, though the parameter distinctions between create and batch_create are noted.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WilliamMo101/lark-hermes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server