Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_remove_group_member

Remove a user from a Yuque group to manage team access and permissions within the knowledge base.

Instructions

Remove a member from a group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.
userIdYesYuque user ID.

Implementation Reference

  • src/tools.js:460-463 (handler)
    The handler function for removing a member from a group using the Yuque client.
    yuque_remove_group_member: async (args, client) => {
  await client.removeGroupMember(args.login, args.userId);
  return jsonText({ ok: true, login: args.login, userId: args.userId });
},
  • src/tools.js:371-382 (schema)
    The definition and schema for the yuque_remove_group_member tool.
    {
  name: "yuque_remove_group_member",
  description: "Remove a member from a group.",
  inputSchema: {
    type: "object",
    properties: {
      login: schemaProperty("string", "Group login."),
      userId: schemaProperty("number", "Yuque user ID.")
    },
    required: ["login", "userId"]
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, placing the full burden of behavioral disclosure on the description. The description fails to disclose that this is a destructive operation (irreversible removal), whether the user’s content is reassigned or deleted, or what error occurs if the userId is not a member.

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?

The single sentence 'Remove a member from a group.' is efficiently structured and front-loaded with the action verb. It contains no redundant words, though it is arguably underspecified given the tool's destructive nature and lack of annotations.

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

Completeness2/5

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

For a destructive group management operation with no annotations and no output schema, the description is inadequate. It omits critical safety context such as permission requirements, cascade effects on user data, and confirmation that the operation permanently severs the group relationship.

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?

With 100% schema description coverage, the schema already fully documents both parameters ('Group login' and 'Yuque user ID'), establishing the baseline of 3. The description adds minimal semantic value beyond mapping 'group' and 'member' to these parameters.

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 the specific verb 'Remove' with the clear resource 'member from a group,' accurately describing the operation. However, it does not distinguish from the sibling tool `yuque_update_group_member` (which modifies membership roles rather than removing entirely), which could cause selection confusion.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., `yuque_update_group_member`), no prerequisites (such as requiring the user to be a current member), and no warnings about irreversibility.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MichealJou/yuque-mcp-plus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server