Skip to main content
Glama

文档/文件夹的协作者(加人、看谁有权限、移除)

feishu_permission_member

Add, list, or remove Feishu cloud document collaborators and set view, edit, or full-access permissions using the document token.

Instructions

管云文档的协作者。action=add 把一个人加进协作者(perm=view 可读 / edit 可编辑 / full_access 可管理);action=list 看现在有哪些人、各自什么权限;action=remove 移除一个人。member_type=openid 时 member_id 传 open_id(ou_ 开头),先 feishu_user_lookup 拿到。注意 token 是云文档 token,不是消息附件。

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": {
      "action": "<action>",
      "token": "<token>"
    },
    "name": "feishu_permission_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
permNoaction=add 时的权限,默认 view。
typeNo资源类型,默认 docx。
tokenYes云文档/文件夹 token。
actionYesadd 加人、list 看权限、remove 移除。
member_idNoaction=add/remove 时用:对方的 open_id 等。
member_typeNoaction=add/remove 时用,默认 openid。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and openWorldHint=true, so the description adds real value: it discloses the destructive remove action, the permission tiers applied on add, and the easy-to-confuse 'cloud doc token vs attachment token' distinction. It stops short of saying what caller permissions are required or whether removal is reversible.

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 tight clauses covering add/list/remove, then two short caveats, with the central action mapping front-loaded. Nothing is padded, though the sentences are dense with semicolon-separated sub-clauses.

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

Completeness4/5

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

For a 6-parameter, enum-heavy tool with no output schema, the description covers all three action modes, the permission enum, and the identity-resolution step, which is what an agent needs before calling. It omits what list returns and any caller-permission requirement, which are the remaining minor gaps.

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 all six parameters are already documented in the schema, and the description largely restates those same meanings (perm applies to add, member_id is the open_id). It adds only marginal detail beyond the schema, such as the ou_ prefix convention, which lands at the baseline.

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 opening sentence names the resource (cloud-doc collaborators) and the description enumerates the three concrete operations (add/list/remove) with the permission levels each supports. The closing note that the token is a cloud-document token, not a message-attachment token, implicitly separates it from chat/file siblings, though no sibling is named explicitly.

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?

Each action value is glossed with its intent (add a person, see who has access and at what level, remove a person), and the description gives a concrete prerequisite: when member_type=openid, resolve the ou_ value via feishu_user_lookup first. No explicit when-not or ownership/precondition guidance is given.

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