Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_list_doc_versions

Retrieve all historical versions of a Yuque document to track changes, review edits, or restore previous content using the document ID.

Instructions

List all versions of a document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docIdYesYuque doc ID.

Implementation Reference

  • src/tools.js:456-456 (handler)
    The handler function for the yuque_list_doc_versions tool.
    yuque_list_doc_versions: async (args, client) => jsonText(await client.listDocVersions(args.docId)),
  • src/tools.js:326-334 (registration)
    The registration definition for the yuque_list_doc_versions tool.
    name: "yuque_list_doc_versions",
description: "List all versions of a document.",
inputSchema: {
  type: "object",
  properties: {
    docId: schemaProperty("number", "Yuque doc ID.")
  },
  required: ["docId"]
}

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, description carries full disclosure burden but states only the basic operation. Missing: pagination behavior, sort order (chronological?), maximum versions returned, and whether current version is included.

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?

Six-word description is efficiently front-loaded with no redundancy. However, brevity leaves behavioral gaps given lack of annotations and output schema.

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

Completeness3/5

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

Minimum viable for a single-parameter list operation with no output schema. Would benefit from stating what version metadata (timestamp, author, etc.) is returned in the list.

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% (docId is fully documented as 'Yuque doc ID'), establishing baseline 3. Description adds no additional parameter context (e.g., where to find this ID).

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 specific verb (List) and resource (document versions). Plural 'versions' implicitly distinguishes from sibling 'yuque_get_doc_version' (singular), though explicit comparison would strengthen this.

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 guidance provided on when to use this versus 'yuque_get_doc_version' or prerequisites for accessing version history.

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