Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_get_repos

Retrieve Yuque knowledge base repositories for current or specified users and groups to manage content hierarchies and document structures.

Instructions

List Yuque repositories for the current user or a specified user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdNoOptional Yuque user ID.
ownerTypeNoOptional owner type.
ownerLoginNoOptional owner login. When provided, ownerType decides /users/{login}/repos or /groups/{login}/repos.

Implementation Reference

  • src/tools.js:434-435 (handler)
    The handler function for 'yuque_get_repos' which calls the client's getRepos method.
    yuque_get_repos: async (args, client) =>
  jsonText(await client.getRepos(args.ownerLogin ? args : args.userId)),
  • src/tools.js:97-107 (schema)
    The schema definition for 'yuque_get_repos'.
      name: "yuque_get_repos",
  description: "List Yuque repositories for the current user or a specified user.",
  inputSchema: {
    type: "object",
    properties: {
      userId: schemaProperty("string", "Optional Yuque user ID."),
      ownerType: schemaProperty("string", "Optional owner type.", { enum: ["user", "group"] }),
      ownerLogin: schemaProperty("string", "Optional owner login. When provided, ownerType decides /users/{login}/repos or /groups/{login}/repos.")
    }
  }
},

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. Only states 'List' implying read-only, but omits pagination behavior, rate limits, result ordering, or what data fields are returned. Does not clarify that all parameters are optional with complex interdependencies.

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 of 11 words is appropriately concise and front-loaded with the action verb. However, extreme brevity leaves gaps given the tool has 3 optional parameters with non-obvious interactions.

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?

Insufficient for a tool with 3 optional parameters and ambiguous sibling relationships. Lacks output guidance (no output schema), pagination info, and fails to resolve the apparent redundancy with 'yuque_list_repos'.

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 adequate field descriptions. Description adds context 'current user or a specified user' which loosely maps to parameters, but does not explain parameter relationships (userId vs ownerLogin) or when to use ownerType. Baseline 3 appropriate given schema quality.

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 'Yuque repositories' with scope 'for the current user or a specified user'. However, fails to distinguish from sibling tool 'yuque_list_repos' which appears to serve an identical purpose based on naming.

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 explicit guidance on when to use versus alternatives (particularly 'yuque_list_repos' or 'yuque_get_repo'), no prerequisites mentioned, and no guidance on parameter selection between userId vs ownerLogin/ownerType.

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