Skip to main content
Glama

建一个群

feishu_chat_create

Creates a Feishu group chat and adds specified members using open_id values, with an option to start as an empty group. Use it to set up a bot-owned conversation for follow-up messages or management.

Instructions

新建群并把指定的人拉进来。机器人建完就是群主,后续能改群名、发消息、置顶。成员要用 open_id(ou_ 开头);不确定 id 先用 feishu_user_lookup 查。

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

Input Schema

NameRequiredDescriptionDefault
nameYes群名。
descriptionNo群描述。
member_open_idsNo初始成员 open_id 列表(ou_ 开头)。可以不传,建空群。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint=false and openWorldHint=true, the description discloses a consequential side effect: the bot becomes the group owner and can later rename, post, and pin. That is useful privilege context that the annotations do not carry; rate limits and whether members are notified remain undisclosed.

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?

Three compact sentences: the action comes first, the ownership outcome second, and the parameter prerequisite last. The middle sentence about renaming, messaging, and pinning is slightly tangential but earns its place by establishing ownership.

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?

For a create tool with no output schema, the description never says what comes back, such as the new group's id, which an agent needs for follow-up calls. Requirements such as name and the optional member list are otherwise adequately implied for a 3-parameter 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 name, description, and member_open_ids are already documented, including the ou_ prefix format. The description adds only the 'look it up first' tip, which duplicates the schema's format note rather than extending semantics, so the baseline 3 applies.

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 uses a specific verb and resource ('新建群并把指定的人拉进来') and adds scope about what the caller can do afterwards, so an agent can tell it apart from feishu_chat_update or feishu_chat_dissolve without opening any schema. It does not explicitly name the sibling it is not, which keeps it just under the top mark.

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 provides one explicit conditional routing rule: if the member id is uncertain, call feishu_user_lookup first. However, there is no guidance on when creating a group is preferable to other approaches, and there are no exclusions or prerequisites such as permission requirements.

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