wiki_batch_delete
Delete multiple wiki documents at once by providing a list of document IDs.
Instructions
批量删除多个文档。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| doc_ids | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Delete multiple wiki documents at once by providing a list of document IDs.
批量删除多个文档。
| Name | Required | Description | Default |
|---|---|---|---|
| doc_ids | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It only states 'delete' without disclosing irreversible behavior, permission requirements, or partial failure handling. The output schema exists but is unused.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no unnecessary words, but it lacks structure and is too terse to convey meaningful usage information. It is minimally acceptable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of batch deletion (potential partial failures, side effects) and the existence of an output schema, the description is severely incomplete. No information about response, error handling, or post-conditions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The sole parameter 'doc_ids' has 0% schema description coverage, and the description offers no clarification on format, limits, or error behavior. The name is suggestive but insufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '批量删除多个文档' (Batch delete multiple documents) clearly states the action (delete), resource (documents), and batch nature, distinguishing it from the sibling 'wiki_delete_document' which handles single deletes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like 'wiki_delete_document', or on prerequisites such as permissions or reversibility. The agent has no explicit context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ispace-top/mcp-server-ispace-wiki'
If you have feedback or need assistance with the MCP directory API, please join our Discord server