Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_list_group_members

Retrieve all members of a Yuque group or team to manage access permissions and collaboration within knowledge bases.

Instructions

List all members of a group or team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.

Implementation Reference

  • src/tools.js:458-458 (handler)
    The handler function for the yuque_list_group_members tool.
    yuque_list_group_members: async (args, client) => jsonText(await client.listGroupMembers(args.login)),
  • src/tools.js:347-357 (schema)
    The schema registration for the yuque_list_group_members tool.
    {
  name: "yuque_list_group_members",
  description: "List all members of a group or team.",
  inputSchema: {
    type: "object",
    properties: {
      login: schemaProperty("string", "Group login.")
    },
    required: ["login"]
  }
},

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 description carries full burden, yet it omits pagination behavior, return data structure, authentication requirements, and rate limits.

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?

Single sentence with no redundancy, though arguably too minimal given the lack of annotations and output schema.

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?

Without an output schema, the description fails to indicate what member data is returned (e.g., user IDs, names, roles) or pagination behavior, leaving significant gaps for an API listing tool.

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 has 100% description coverage for the single 'login' parameter. Description adds no additional parameter context, but none is needed given complete schema documentation.

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?

Clear verb (List) and resource (members of a group/team), but does not explicitly differentiate from sibling yuque_group_member_stats which handles statistics rather than member listings.

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?

Provides no guidance on when to use this tool versus alternatives like yuque_group_member_stats, nor prerequisites for accessing group membership data.

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