Skip to main content
Glama

batch_delete_documents

DestructiveIdempotent

Delete multiple documents at once, moving them to trash or permanently removing them. Handles errors automatically and applies rate limiting for bulk operations.

Instructions

Deletes multiple documents, moving them to trash or permanently.

This tool processes each document sequentially, continuing even if individual operations fail. Rate limiting is handled automatically.

IMPORTANT: When permanent=False (the default), documents are moved to trash and retained for 30 days. Setting permanent=True bypasses trash and immediately deletes documents without recovery option.

Use this tool when you need to:

  • Remove multiple unwanted documents at once

  • Clean up workspace in bulk

  • Permanently delete sensitive information (with permanent=True)

Recommended batch size: 10-50 documents per operation

Args: document_ids: List of document IDs to delete permanent: If True, permanently deletes without recovery option

Returns: Summary of batch operation with success/failure details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idsYes
permanentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Explains sequential processing, continuation on failure, automatic rate limiting, and the behavior of permanent=false (trash, 30-day retention) vs. permanent=true (immediate deletion). Annotations confirm destructiveHint=true and idempotentHint=true, with no contradiction.

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?

Well-structured with clear sections, bold note, bullet points, and parameter descriptions. Every sentence adds value without redundancy.

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?

Covers all aspects: purpose, usage, behavior, parameters, and return value. Output schema is referenced (summary of operation), and the description is adequate for an agent to correctly invoke the tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains both parameters: document_ids as list of IDs, permanent as toggle for full deletion. This adds meaning beyond the schema's minimal metadata.

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 it deletes multiple documents with options for trash or permanent deletion. It distinguishes from siblings like delete_document (single) and archive_document by specifying batch operation.

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

Usage Guidelines5/5

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

Provides explicit use cases (bulk removal, workspace cleanup, permanent delete of sensitive data) and a recommended batch size. Implicitly differentiates from single-document operations.

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/fastmcp-me/mcp-outline'

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