Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_create_repo

Create a repository in the Yuque knowledge base to organize documents and manage content hierarchies. Specify name, visibility, owner, and description for structured knowledge management.

Instructions

Create a repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRepository name.
slugNoOptional repository slug.
descriptionNoOptional repository description.
isPublicNoWhether the repository is public.
ownerTypeNoOwner type.
ownerLoginNoOwner login for user or group repo creation.

Implementation Reference

  • src/tools.js:452-452 (handler)
    The handler function for the yuque_create_repo tool.
    yuque_create_repo: async (args, client) => jsonText(await client.createRepo(args)),
  • src/tools.js:272-286 (registration)
    The registration and schema definition for the yuque_create_repo tool.
    {
  name: "yuque_create_repo",
  description: "Create a repository.",
  inputSchema: {
    type: "object",
    properties: {
      name: schemaProperty("string", "Repository name.", { minLength: 1 }),
      slug: schemaProperty("string", "Optional repository slug."),
      description: schemaProperty("string", "Optional repository description."),
      isPublic: schemaProperty("boolean", "Whether the repository is public."),
      ownerType: schemaProperty("string", "Owner type.", { enum: ["user", "group"] }),
      ownerLogin: schemaProperty("string", "Owner login for user or group repo creation.")
    },
    required: ["name"]
  }

Tool Definition Quality

D1.7/5.0
Behavior1/5

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

With no annotations provided, the description carries the full disclosure burden but offers no behavioral details. It omits critical mutation context: error handling for duplicate names, whether the operation is atomic, required authentication scope, or what distinguishes success from failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While brief (three words), the description is under-specified rather than appropriately concise. For a 6-parameter mutation tool with no annotations, this length fails to front-load essential behavioral or contextual information, leaving the agent under-informed.

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

Completeness1/5

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

Severely inadequate for a creation tool with owner-type enums and public/private flags. No output schema, annotations, or description text explains return values, side effects, or the relationship between ownerLogin and ownerType fields.

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?

The input schema has 100% description coverage with clear field definitions (name, slug, ownerType, etc.). The description adds no parameter-specific guidance, but with comprehensive schema documentation, the baseline score of 3 is appropriate per rubric guidelines.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

The description 'Create a repository.' is a tautology that merely restates the tool name in verb-noun form. It fails to specify what constitutes a repository in the Yuque context (knowledge base vs. code repository) and does not differentiate from sibling tools like yuque_update_repo or yuque_create_doc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 (e.g., yuque_update_repo), nor prerequisites such as required permissions or ownership constraints. The agent receives no signals about workflow context.

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