Skip to main content
Glama
Sign In
Feishu MCP Server

Feishu MCP Server

by shou-nian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_feishu_bitable_records

Paginate query Feishu Bitable records with optional filter expressions to locate target rows and retrieve record_id for precise updates.

Instructions

分页查询飞书多维表格记录，可传入 Bitable filter 表达式定位目标行；返回用于精确更新的 record_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>"
    },
    "name": "list_feishu_bitable_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
table_idYesBitable table_id（数据表 ID）
app_tokenYesBitable app_token（多维表格 Token）
page_sizeNo每页记录数，范围 1—500
page_tokenNo
filter_expressionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description discloses pagination support, filter capability, and that the result includes record_id for updates. It adds value beyond the schema by explaining the purpose of filter_expression and return value.

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

Conciseness5/5

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

The description is a single sentence that efficiently conveys the core action and key features without extraneous information.

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?

Given the complexity of pagination and filtering, the description provides sufficient context. The presence of an output schema reduces the need to describe return values in detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover all parameters (100% coverage), but the tool description adds context about filtering to locate target rows and returning record_id, which enhances understanding of parameter usage.

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 clearly states the tool paginates Feishu Bitable records, with optional filter expressions, and returns record IDs for updates. This distinguishes it from siblings like create/update/list fields.

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 implicitly indicates usage for reading records with pagination and filtering. While no explicit when-not-to-use or alternatives are given, the context from siblings (create, update) makes its role clear.

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

Deploy Server

Other Tools