Skip to main content
Glama
Sign In
mcp-paperless-ngx

mcp-paperless-ngx

by tobee89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete documents

delete_documents
Destructive

Move multiple documents to trash at once, recoverable until the trash is emptied. Requires explicit confirmation of the exact document IDs before execution.

Instructions

Move several documents to the trash at once. Recoverable until the trash is emptied. Requires explicit user confirmation — list what will be deleted before calling this.

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": {
      "documents": "<documents>"
    },
    "name": "delete_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentsYesIDs of the documents to act on. Always an explicit list — never an unbounded selection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds crucial context: the action is recoverable until trash is emptied, and it requires user confirmation. It also clarifies the batch scope. This goes beyond the structured annotations without contradicting them.

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?

Three short sentences: action+scope, recoverability, and the confirmation requirement. Every sentence earns its place and critical safety info is front-loaded in the first sentence.

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?

For a batch destructive tool with one well-schematized parameter, the description fully covers what an agent needs: what will happen, recoverability, confirmation requirement, and the explicit-list constraint. No output schema is present, but return-value details aren't critical for correct invocation.

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 100% and the single parameter is well documented in the schema. The description reinforces the explicit-list nature with 'several documents' and aligns with 'always an explicit list'. Slight deduction because it doesn't add additional format details, but the schema already carries the load.

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 states a specific verb ('Move'), a precise resource ('documents'), and the action's effect ('to the trash at once'). It distinguishes from the sibling 'delete_document' by signaling batch operation ('several documents'), and from 'empty_trash'/'restore_from_trash' by explicitly framing trash as recoverable.

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?

Explicitly instructs that explicit user confirmation is required and that the tool must not be invoked without first listing what will be deleted. This provides a clear when-to-use and a safety gate, which is especially important given the destructive annotation.

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