Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_delete_repo

Delete a Yuque repository by specifying its ID or namespace to remove unwanted knowledge base content from the platform.

Instructions

Delete a repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoIdNoYuque repository ID.
repoNamespaceNoYuque repository namespace.

Implementation Reference

  • src/yuque-client.js:261-266 (handler)
    The actual implementation of the deleteRepo method which makes the API call.
    async deleteRepo(refs = {}) {
  const repoRef = await this.resolveRepoIdentifier(refs);
  return this.request(`/repos/${repoRef}`, {
    method: "DELETE"
  });
}
  • src/tools.js:302-309 (registration)
    The tool definition registration for "yuque_delete_repo".
    {
  name: "yuque_delete_repo",
  description: "Delete a repository.",
  inputSchema: {
    type: "object",
    properties: repoRefSchema()
  }
},
  • src/tools.js:454-454 (handler)
    The tool handler function mapping for "yuque_delete_repo".
    yuque_delete_repo: async (args, client) => jsonText(await client.deleteRepo(args)),

Tool Definition Quality

C2.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure. While 'Delete' implies destruction, it fails to disclose critical behavioral traits: whether the deletion is permanent/irreversible, whether child documents are cascade-deleted or orphaned, and what authorization is required. This gap is dangerous for a destructive operation.

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

Conciseness3/5

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

Extremely brief (3 words). While it wastes no words, it is under-specified rather than elegantly concise. The brevity fails to front-load critical safety information for a destructive action.

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 destructive repository operation. With no output schema and no annotations, the description should explain the relationship between the two identification parameters (ID vs namespace) and cascade behavior. It provides none of this context.

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% (repoId and repoNamespace are both documented). The description adds no additional parameter clarifications (e.g., whether both are required or if one suffices for identification), meeting the baseline expectation when the schema is complete.

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?

States the obvious ('Delete a repository' restates the function name yuque_delete_repo). While it identifies the resource type (distinguishing from siblings like delete_doc), it adds minimal semantic value beyond the name itself, bordering on tautology.

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?

Provides no guidance on when to use this versus alternatives (e.g., when to archive vs delete), no prerequisites (ownership/permissions), and no warning about the consequences for contained documents.

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