Skip to main content
Glama
Sign In
feishu-user-plugin

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_group

Creates a new group chat with a bot, allowing optional addition of initial members.

Instructions

[Official API] Create a new group chat (as bot). Can add initial members.

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": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesGroup name
descriptionNoGroup description (optional)
user_idsNoInitial member open_ids (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden for behavioral disclosure. It only states the creation action and the ability to add initial members, but does not disclose side effects, permission requirements, whether the bot is automatically added, or any return values. For a mutation tool, this is a significant gap.

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 two short sentences with no redundancy. It front-loads the core purpose and includes a useful optional capability. Every word earns its place.

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?

Given it is a simple creation tool with three parameters and no output schema, the description covers the basic action but omits usage context, behavioral details, and return expectations. It is minimally viable but leaves clear gaps in guidance and behavioral transparency.

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 the schema already documents all parameters. The description adds a minor hint about 'initial members' which maps to the user_ids parameter, but does not provide new meaning beyond the schema. Baseline 3 is appropriate.

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 action: 'Create a new group chat (as bot).' It uses a specific verb and resource, and the addition 'Can add initial members' further clarifies scope. It distinguishes itself from siblings like create_p2p_chat by explicitly targeting group chats.

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

Usage Guidelines2/5

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

No explicit guidance is given on when to use this tool vs. alternatives such as create_p2p_chat or send_to_group. The 'as bot' phrasing implicitly indicates bot context, but there is no mention of prerequisites, exclusions, or when another tool would be more appropriate.

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