Skip to main content
Glama
Sign In
Feishu MCP Server

Feishu MCP Server

by shou-nian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

copy_feishu_bitable_dashboard

Create a new Feishu Bitable dashboard by copying an existing template, including all its components.

Instructions

通过官方复制接口从已有仪表盘模板创建新仪表盘，并复制模板中的全部组件。

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

Input Schema

NameRequiredDescriptionDefault
nameYes复制后新仪表盘的名称
app_tokenYesBitable app_token（多维表格 Token）
source_block_idYes作为复制模板的仪表盘 block_id

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and that it copies all components, but fails to mention any side effects, permission requirements, or limitations. For a mutation tool, more details are needed.

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, efficient sentence. It is front-loaded with the method and then describes the action. No redundant or unnecessary words.

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

Completeness3/5

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

While the tool has a clear purpose and schema descriptions, the description does not cover behavioral aspects or output expectations. An output schema exists, so return values are documented elsewhere, but additional context about prerequisites or the effect on the source template would improve completeness.

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 description coverage is 100%, so baseline is 3. The overall description adds no extra parameter semantics beyond what the schema already provides. The schema descriptions for each parameter are clear and adequate.

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 explicitly states the action (creating a new dashboard by copying), the resource (an existing dashboard template), and the extent (copies all components). It clearly distinguishes from sibling tools like read or create, as none other perform a copy operation.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. While the purpose is clear, there is no guidance on prerequisites or exclusions. Usage is implied but not directive.

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