Skip to main content
Glama

edit_documents_bulk

Destructive

Apply one operation (retag, reassign, delete, reprocess) to many selected Paperless documents at once. Pick documents by IDs or filters and update them in a single bulk action.

Instructions

Apply ONE of a fixed set of operations to MANY documents at once. Methods: set_correspondent, set_document_type, set_storage_path, add_tag, remove_tag, modify_tags, modify_custom_fields, set_permissions, delete, reprocess, merge, split, rotate, delete_pages, edit_pdf, remove_password. For per-document field edits including title, content, created (date), archive_serial_number, or owner, use update_document instead — those fields are not editable here. Note: 'remove_tag' only removes the tag from the specified documents (tag stays in the system); 'delete_tag' permanently deletes the tag from the entire system. ⚠️ WARNING: method 'delete' permanently deletes documents and requires confirm=true. Select documents either by documents (IDs) or by all: true + filters — Paperless document filter names such as correspondent__id, tags__id__all, document_type__id, title_content, created__date__gte or query (full text); the filter form changes every matching document in one call, e.g. reassigning all documents from a duplicate correspondent before deleting it. Unknown filter keys are refused, and the result reports matched_documents. all=true is not supported for merge, split, delete_pages, edit_pdf or remove_password. Method remove_password strips a PDF password (needs password); with update_document=true the unlocked file is stored as a new version of the same document. Method reprocess accepts remote_ocr=true to use the configured remote OCR engine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoSelect every document matching `filters` instead of listing IDs
tagNo
mergeNoWhen true with set_permissions, merges with existing permissions instead of replacing.
ownerNoOwner user ID for set_permissions method (null clears the owner).
pagesNo
methodYes
confirmNoMust be true when method is 'delete' to confirm destructive operation
degreesNo
filtersNoWith all=true (required then): Paperless document filters, e.g. {"correspondent__id": 12}, {"tags__id__all": "3,4"}, {"document_type__id": 5}, {"title_content": "invoice"}. Not list_documents' tool arguments: use correspondent__id, not correspondent. Unknown keys are refused.
add_tagsNo
passwordNoremove_password: the PDF's password
documentsNoDocument IDs to change. Omit when selecting with all + filters.
operationsNoPer-page operations for edit_pdf method. Each entry: {page, rotate?, doc?}.
remote_ocrNoreprocess: OCR with the remote OCR engine configured in Paperless instead of the local one (default false)
remove_tagsNo
storage_pathNo
correspondentNo
document_typeNo
delete_originalNoremove_password / edit_pdf: delete the original after writing a separate new document (ignored with update_document=true)
set_permissionsNoPermission grants for set_permissions method. view/change each take user and group ID lists.
update_documentNoedit_pdf / remove_password: store the result as a new version of the same document instead of creating a new document (default false).
delete_originalsNo
include_metadataNoedit_pdf / remove_password: copy metadata to the new document (default true).
add_custom_fieldsNo
excluded_documentsNoWith all=true: IDs to leave out of the selection
metadata_document_idNo
remove_custom_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false. The description adds valuable context: the 'delete' method requires confirm=true and permanently deletes, remove_tag vs delete_tag semantics, and all=true limitations. Some method-specific behaviors (e.g., merge, split) aren't detailed, but the most critical destructive aspects 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 long but dense with essential information for a complex 27-parameter tool. It's front-loaded with the core purpose, then flows logically through methods, selection, destructive warnings, and specific method notes. While not bulleted, it remains scannable and every sentence contributes value.

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?

Given the tool's complexity (27 params, no output schema), the description covers the most critical aspects: method list, selection modes, destructive warnings, and key parameter formats. However, it doesn't explain every method's parameters or return behavior, leaving some gaps for the agent to infer. Still, it's remarkably complete for such a large tool.

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 52%, so the description carries partial burden. It explains filters format with examples, confirms the requirement for delete, and details custom field value formats (monetary/documentlink). This adds meaning beyond the schema, though many parameters (e.g., degrees, pages) remain undocumented. Overall, it compensates well for the coverage 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 clearly states the tool applies one of a fixed set of operations to many documents at once, listing all methods. It explicitly differentiates from update_document for per-document field edits, making its purpose and scope unambiguous.

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 when-to-use guidance: names update_document as the alternative for per-document field edits, warns that all=true is not supported for certain methods, and clarifies selection via documents vs. all+filters. This gives clear routing to the correct tool.

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

Deploy Server

Other Tools