siyuan-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_blocks_content

Retrieve full content of multiple blocks in one batch, reducing API calls. Individual failures are returned as error fields without interrupting the whole operation.

Instructions

批量获取多个块的完整内容。

适用场景: - 一次性拉取多个块内容，减少多次调用开销。

注意事项: - 单个块失败不会中断整体，失败项会返回 error 字段。 - 返回的 kramdown 与 get_block_content 一样会做敏感信息打码。

Args: block_ids (List[str]): 块 ID 列表

Returns: List[Dict[str, Any]]: 包含每个块内容的字典列表

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": {
      "block_ids": "<block_ids>"
    },
    "name": "get_blocks_content"
  }
}

Input Schema

Name	Required	Description	Default
`block_ids`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.31.0Sep 20, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses partial-failure semantics ('单个块失败不会中断整体，失败项会返回 error 字段') and sensitive-information masking in kramdown output, both of which are valuable beyond the schema. It does not mention auth, rate limits, or ordering, but the key quirks are covered.

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?

The description is organized into compact labeled sections (适用场景, 注意事项, Args, Returns) and every section contributes operational information. The Args section is somewhat redundant with the schema, but overall the structure is clear and front-loaded with the core purpose.

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?

With a single self-evident parameter and an output schema present, the description adds the important contextual details an agent needs: batch usage rationale, per-block partial failure, the error field, and sensitive-information masking. It could additionally mention batch-size limits or how error values are represented, but it is sufficiently complete for correct selection and invocation.

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

Parameters2/5

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

The schema has 0% description coverage for the only parameter, and the Args section mostly restates the schema: 'block_ids (List[str]): 块 ID 列表'. This adds no meaningful constraints or semantics such as maximum batch size, duplicate handling, ordering, or required behavior, so the description does not compensate for the schema gap.

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 opens with '批量获取多个块的完整内容', which clearly states a specific verb, resource, and batch scope. It also distinguishes itself from the sibling get_block_content by emphasizing multiple blocks and reduced call overhead, so an agent can tell them apart.

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

Usage Guidelines4/5

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

The description explicitly says it applies to '一次性拉取多个块内容，减少多次调用开销', providing a clear when-to-use context. However, it does not explicitly tell the agent to use get_block_content for single-block fetches or give exclusion criteria, so it stops short of full when-not guidance.

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