yuque-mcp

Overview Schema Source Related Servers Discussions Admin

yuque_get_doc_by_book_id

Retrieve document details from a Yuque knowledge base using the book ID and document ID. Specify optional pagination for comments.

Instructions

通过知识库 ID 获取文档详情

权限要求: read 参数:

book_id: 知识库 ID
id: 文档 ID
page_size: 评论每页数量 (可选)
page: 评论页码 (可选)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "book_id": "<book_id>",
      "id": "<id>"
    },
    "name": "yuque_get_doc_by_book_id"
  }
}

Input Schema

Name	Required	Description	Default
`book_id`	Yes
`id`	Yes
`page_size`	No
`page`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It states the permission requirement, which hints at read-only behavior. However, it does not disclose potential side effects, error handling, or rate limits. The description is adequate but minimal.

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

Conciseness5/5

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

The description is concise, with a clear structure: one line for purpose, one line for permission, and a bulleted list of parameters. No unnecessary words or repetitions.

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

Completeness4/5

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

Given that an output schema exists (not shown), the description does not need to explain return values. It covers the permission and parameter meanings. However, it lacks information on error scenarios or pagination behavior beyond comments. Overall, it is fairly complete for a simple retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds Chinese labels for each parameter (e.g., 'book_id: 知识库 ID', 'page_size: 评论每页数量'). This provides context beyond the schema titles. It does not explain formats or allowed values, but for the optional pagination parameters, it clarifies they relate to comments.

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

Purpose5/5

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

The description clearly states the action ('获取文档详情' means 'get document details') and the resource ('通过知识库 ID' means 'by knowledge base ID'). It distinguishes from siblings like yuque_get_doc (likely by document ID) and yuque_get_docs (list docs).

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions permission requirement ('权限要求: read') but does not provide explicit guidance on when to use this tool versus alternatives, nor does it specify exclusions or prerequisites beyond the required parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server