Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_update_group_member

Modify user roles within Yuque knowledge base groups by adjusting permissions for members, admins, or owners to manage collaborative access.

Instructions

Update a group member role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.
userIdYesYuque user ID.
roleYesRole: 0 member, 1 admin, 2 owner.

Implementation Reference

  • src/tools.js:459-459 (handler)
    Handler implementation for 'yuque_update_group_member' which calls 'client.updateGroupMember'.
    yuque_update_group_member: async (args, client) => jsonText(await client.updateGroupMember(args.login, args.userId, args.role)),
  • src/tools.js:359-370 (schema)
    Tool schema definition for 'yuque_update_group_member'.
      name: "yuque_update_group_member",
  description: "Update a group member role.",
  inputSchema: {
    type: "object",
    properties: {
      login: schemaProperty("string", "Group login."),
      userId: schemaProperty("number", "Yuque user ID."),
      role: schemaProperty("number", "Role: 0 member, 1 admin, 2 owner.")
    },
    required: ["login", "userId", "role"]
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description carries the full burden of behavioral disclosure. It fails to mention permission requirements, preconditions (that the user must already be a group member), idempotency, or side effects of the mutation.

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?

Single sentence with five words, zero redundancy, immediately conveys the core action without extraneous information.

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?

Inadequate for a mutation tool with no annotations or output schema. Missing critical context about authentication requirements, authorization levels needed to modify roles, and expected behavior when the target user is not already a member.

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% with clear descriptions for all three parameters (login, userId, role with value mappings). The description adds minimal semantic value beyond what the schema already provides, meeting the baseline for high-coverage schemas.

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?

"Update a group member role" provides a clear verb (update) and resource (group member role). However, it does not differentiate from sibling yuque_remove_group_member or clarify when to update roles versus remove members entirely.

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 guidance provided on when to use this tool versus alternatives, prerequisites (e.g., requiring admin/owner permissions), or expected workflows for role management.

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