moki-whiteboard

Overview Schema Source Related Servers Discussions Admin

删除白板元素

whiteboard_delete_elements

DestructiveIdempotent

Deletes specific whiteboard elements by their listed IDs without removing pages or entire boards. Use it to clean up selected items while preserving the rest of the canvas.

Instructions

Delete only the explicitly listed element IDs, not pages or entire boards. 仅删除明确给出的元素 ID。不会删除页面或整个白板。

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": {
      "ids": "<ids>"
    },
    "name": "whiteboard_delete_elements"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes
`boardId`	No	白板 ID；省略时使用最近更新的白板，建议始终指定准确 ID	default
`expectedVersion`	No	先 inspect 获得版本；过期写入会返回 VERSION_CONFLICT 而不会覆盖内容

Output Schema

Name	Required	Description	Default
`board`	No
`error`	No
`boards`	No
`pageId`	No
`boardId`	No
`current`	No
`deleted`	No
`version`	No
`alignedIds`	No
`deletedIds`	No
`elementIds`	No
`updatedIds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Oct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by naming what will NOT be destroyed (pages, boards), which reduces the chance of an over-broad delete.

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?

Two short, front-loaded sentences that each carry the same scoping constraint in English and Chinese. Efficient, though the bilingual restatement doubles length without adding new information.

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?

For a destructive, 3-parameter tool with rich annotations and an output schema, the description covers scope and non-targets adequately. Minor gaps remain: it doesn't mention the 200-ID cap or that expectedVersion should be obtained via whiteboard_inspect before calling.

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 coverage is 67%: boardId and expectedVersion are described in-schema, but the required 'ids' parameter has no description. The description compensates by clarifying that ids means explicit element identifiers and is the sole deletion target, which is meaningful for the undocumented required parameter.

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?

Specific verb (delete) plus resource (elements) plus an explicit scope boundary: only listed element IDs, not pages or whole boards. That boundary directly separates it from siblings whiteboard_delete_board and whiteboard_manage_pages.

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 'not pages or entire boards' clause implicitly routes the agent to the page/board siblings, giving clear usage context. It stops short of stating prerequisites such as needing IDs from whiteboard_inspect or when to prefer whiteboard_update_elements instead.

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

Deploy Server