Skip to main content
Glama

会话成员名单

feishu_members
Read-only

List members of a Feishu chat or group with names and open_ids to check who is present, get open_ids for mentions or direct messages, and verify group size.

Instructions

列出某个会话(群/单聊)里的成员,返回名字 + open_id。适合:确认某人在不在群里、拿到 open_id 用于 @ 或私聊、核对群规模。不适合:只是想看有哪些群(用 feishu_chats);想读聊天内容(用上下文相关工具)。chat_id 不填时用 FEISHU_DEFAULT_CHAT_ID;两者都没有会直接报错说明。只返回文本,不往飞书发消息。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "feishu_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo最多返回多少个成员,默认 50,上限 100(超过按 100 处理)。
chat_idNo要查成员的会话 chat_id(oc_ 开头)。不填则用默认会话 FEISHU_DEFAULT_CHAT_ID。

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 and openWorldHint, so the description's added note that it sends nothing to Feishu is corroborating but useful. The genuinely additive details are the fallback to FEISHU_DEFAULT_CHAT_ID when chat_id is omitted and the explicit failure when neither is available — real runtime behavior not in the annotations.

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 structured into 适合 / 不适合 buckets and a defaults/error clause — easy to scan. Slightly dense with parenthetical examples, and the closing '只返回文本,不往飞书发消息' partially duplicates the read-only signal, costing a perfect score.

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 two-optional-parameter read tool with no output schema, the definition covers what is returned (name + open_id), the default-resolution order, and the error condition. Nothing an agent needs in order 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 both parameters are fully documented in the schema, so baseline 3 applies. The description restates the chat_id default and adds the failure semantics, but says nothing about limit (default 50, cap 100) beyond what the schema already carries.

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 (list members of a chat/group/single conversation), names the return shape (name + open_id), and covers both chat types. An agent can distinguish it from feishu_chats without opening any schema.

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?

Gives three concrete positive use cases (membership check, obtaining open_id for @ or DM, verifying group size) and two explicit exclusions pointing at the right alternative (feishu_chats for listing chats, context tools for reading content). When-to-use is fully resolved.

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