Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_list_repos

Retrieve repositories from Yuque knowledge base by user ID, owner type, or login to manage content hierarchies and document structures.

Instructions

Alias of yuque_get_repos for compatibility with official naming.

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 actual implementation of the tool, aliased as yuque_list_repos, is defined as yuque_get_repos. It fetches repositories using the Yuque client.
    yuque_get_repos: async (args, client) =>
  jsonText(await client.getRepos(args.ownerLogin ? args : args.userId)),
  • src/tools.js:479-483 (registration)
    Registration of the yuque_list_repos tool as an alias for yuque_get_repos.
    {
  name: "yuque_list_repos",
  description: "Alias of yuque_get_repos for compatibility with official naming.",
  inputSchema: TOOL_DEFINITIONS.find((tool) => tool.name === "yuque_get_repos").inputSchema
},

Tool Definition Quality

C2.4/5.0
Behavior1/5

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

No annotations provided, and description carries the full burden but discloses nothing regarding read-only nature, pagination behavior, rate limits, or return structure despite being a 'list' operation that typically returns collections.

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?

Extremely concise single sentence with no redundancy, though arguably insufficient given the complete absence of behavioral context 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?

With no output schema, no annotations, and three optional filter parameters, the description fails to explain the listing behavior, pagination, or return format. The alias explanation is the only context provided.

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 description coverage is 100%, providing complete documentation of the three optional filtering parameters. Description adds no parameter-specific guidance, 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Identifies the tool as an alias of yuque_get_repos and explains the naming rationale ('compatibility with official naming'), but fails to describe the actual function of listing repositories, requiring inference from the tool name.

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?

Implies interchangeability with yuque_get_repos but provides no explicit guidance on when to prefer this tool versus the canonical version, nor when to use this versus other repository tools like yuque_get_repo (singular).

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