Skip to main content
Glama

查询多维表格记录

feishu_bitable_records
Read-only

Reads records from a Feishu Bitable table with record_id and human-readable field values so you can verify data, locate records to update, or report table contents; supports pagination.

Instructions

读取某个数据表里的记录,每条都带 record_id,并把字段值展开成人话(人员显示名字、附件显示文件名、多选用顿号连接、日期显示原始毫秒值)。适合:核对数据、找要改的那条记录(先查到 record_id 再 update)、给用户汇报表里有什么。record_id 是更新记录的唯一凭据,所以查询结果里一定会带上。limit 默认 50、最大 500;has_more=true 时把返回的 page_token 传回来继续翻页。只返回文本,不修改数据。

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_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo本页最多返回多少条记录,默认 50,上限 500(超过按 500 处理)。
table_idYes数据表 id(形如 tbliz1PrMZkp1DSN)。不知道就先调 feishu_bitable_tables。
app_tokenYes多维表格的 app_token(Base 链接里 /base/ 后面那串)
page_tokenNo翻页令牌:上一次返回 has_more=true 时给出的 page_token,原样传回来取下一页。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=true; the description adds substantial behavior beyond them — exactly how field values are rendered, that record_id is always present as the update credential, the default and maximum page size, and the has_more/page_token continuation contract. It also confirms "只返回文本,不修改数据", which is consistent with the read-only annotation.

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?

Content is front-loaded: what it reads and how results are shaped come first, then use cases, then pagination mechanics. The parenthetical enumeration of field renderings is dense but each item is load-bearing; a slightly tighter phrasing would earn a 5.

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?

Although there is no output schema, the description covers the return shape (record_id per row, humanized field values, has_more/page_token) and the pagination limit, which is everything an agent needs to call and consume results. Nothing material is missing for a 4-parameter read tool.

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 limit (default 50, max 500), page_token, app_token and table_id are already documented in the schema. The description restates the limit bounds and the pagination loop but adds little syntax or meaning beyond them, so the baseline of 3 applies.

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?

The description states a specific verb (读取) and resource (某个数据表里的记录) and immediately distinguishes its output shape: each record carries a record_id and field values are humanized (names for people, filenames for attachments, 、-joined multi-selects, raw ms for dates). An agent can separate this read-records tool from feishu_bitable_update / feishu_bitable_add / feishu_bitable_fields without opening 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 Guidelines4/5

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

It names concrete situations — verifying data, locating the record to change (query first to get record_id, then update), reporting table contents to a user — which routes the agent toward feishu_bitable_update for the write half of the workflow. It lacks an explicit "do not use when..." clause or a contrast with sibling reads like feishu_bitable_tables / feishu_bitable_fields, so it stops short of full exclusions.

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