qbt-kit

delete_torrents

Remove torrents from the qBittorrent queue by hash, with optional downloaded-file deletion and a required confirmation step because the action cannot be undone.

Instructions

Remove torrents. delete_files is never implied: without it the data stays on disk. Requires confirm=True because it cannot be undone.

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": {
      "hashes": "<hashes>"
    },
    "name": "delete_torrents"
  }
}

Input Schema

Name	Required	Description
`hashes`	Yes	torrent hashes to remove. The single value "all" targets EVERY torrent in the queue — pass explicit hashes unless wiping the whole queue is genuinely what was asked.
`confirm`	No	must be true to proceed
`delete_files`	No	also delete the downloaded data

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that deletion is irreversible, that confirmation is required, and that downloaded data remains unless delete_files is set. It could say more about effects on active torrents, but the core destructive behavior is clearly communicated.

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, front-loaded with the core action and immediately followed by the most important safety details. Every sentence earns its place.

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?

For a destructive tool with no annotations, the description covers the critical safety behavior: irreversibility, explicit confirmation, and non-implicit file deletion. Output schema presence means return values need not be explained, and remaining gaps are minor.

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%, so the baseline is 3. The description still adds meaningful semantics by emphasizing that delete_files is never implicitly applied and that data remains on disk without it, which clarifies the practical consequence of the default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Remove torrents.' It clearly identifies the tool's operation, though it does not explicitly contrast it with siblings such as control_torrents or move_torrents.

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

Usage Guidelines3/5

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

It provides important usage constraints: delete_files is not implied and confirm=True is required. However, it does not state when to choose this tool over alternatives like control_torrents, so usage guidance is only implied.

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

This server cannot be deployed