Skip to main content
Glama

多维表格里的数据表

feishu_bitable_tables
Read-only

Lists the data tables in a Feishu Bitable and returns each table_id and name, providing the required identifiers for subsequent field and record operations.

Instructions

列出一张飞书多维表格(Base)里包含哪些数据表,返回每张表的 table_id 与表名。这是所有 bitable 操作的入口:后续查字段、查记录、加记录都要 table_id,而 table_id 只能从这里拿到(用户一般只给 app_token 或一条 Base 链接)。app_token 就是 Base 链接里 /base/ 后面那一串(如 HMr9bcTJcabU8KsD6UGcwVWln9e)。只返回文本,不修改任何数据,可放心在探索阶段调用。不适合:已有 table_id 只是要看字段(用 feishu_bitable_fields);要看记录内容(用 feishu_bitable_records)。

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

Input Schema

NameRequiredDescriptionDefault
app_tokenYes多维表格的 app_token(Base 链接里 /base/ 后面那串,形如 HMr9bcTJcabU8KsD6UGcwVWln9e)

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety claim '不修改任何数据' is partly redundant, but the description adds genuinely new workflow context: that table_id is unobtainable elsewhere and that users typically supply only an app_token or a Base link. It does not cover pagination or behavior with very large Bases, which keeps it below a 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 purpose, then the critical 'this is the entry point' fact, then exclusions, so an agent can stop reading early. Slightly overlong because the app_token explanation duplicates the schema field description and could be trimmed without loss.

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?

For a one-parameter read tool with no output schema, the description covers purpose, return shape (table_id plus table name), the prerequisite relationship to all other bitable tools, and when not to use it. Nothing needed to invoke it correctly 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% and the schema description already explains that app_token is the segment after /base/ with the same example, so the description largely repeats structured data. Its only marginal addition is the observation that users usually provide an app_token or a Base link rather than a table_id, which sets expectations but adds no new syntax or constraints.

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 ('列出一张飞书多维表格(Base)里包含哪些数据表') and names exactly what comes back ('table_id 与表名'). It also distinguishes itself from siblings by explaining that this is the entry point every other bitable operation depends on.

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 gives both directions: call this first because table_id can only be obtained here, and do not call it when a table_id is already known. The exclusions name the concrete alternatives (feishu_bitable_fields for fields, feishu_bitable_records for records) with the condition that selects each.

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