Skip to main content
Glama

batch_delete

Delete multiple files or directories in one operation. Each path is handled independently, with success/failure feedback for every item.

Instructions

Delete multiple files or directories in a single operation. Each path is processed independently, and the tool will report success/failure for each item. / 批量删除多个文件或目录。每个路径独立处理,工具会报告每个项目的成功/失败状态。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYesList of file or directory paths to delete. Each path will be processed independently.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes
successYes
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful traits: 'Each path is processed independently' and 'report success/failure for each item.' However, it does not disclose whether deletions are permanent, require special permissions, or are irreversible, which is a critical gap for a destructive tool.

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 English description is two sentences and front-loaded with the core function. The inclusion of a full Chinese translation is duplicative but not harmful; however, it slightly reduces conciseness since it repeats the same content.

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

Completeness5/5

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

The description is complete for a simple, one-parameter tool. Since an output schema exists, the description doesn't need to explain return values. It explains what the tool does and how it handles multiple paths, which is sufficient for the agent to invoke it correctly.

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%, with a clear description of the 'paths' parameter and examples. The description only restates what the schema already says ('each path will be processed independently'), adding no new semantic meaning.

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 verb and resource: 'Delete multiple files or directories in a single operation.' It distinguishes itself from sibling tools like 'delete', 'delete_file', and 'delete_directory' by explicitly focusing on batch operations on multiple paths.

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 implies usage for batch deletions ('multiple files or directories'), which clearly separates it from single-item delete tools. However, it does not explicitly mention when not to use it or name alternatives, so it falls short of a 5.

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/shibingli/mcp-toolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server