openwebui-mcp-server

openwebui_delete_file

Permanently delete an uploaded file from Open WebUI. If the file is in a knowledge base, remove it from the collection first. Confirmation required.

Instructions

Permanently delete an uploaded file from Open WebUI. If the file is in a knowledge base, remove it from the collection first with openwebui_remove_file_from_knowledge. Requires confirm: true.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "openwebui_delete_file"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	File ID to delete
`confirm`	Yes	Must be true to confirm deletion

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It discloses permanence, the knowledge base removal prerequisite, and the confirm requirement. It doesn't mention permissions or error behavior, but the key behavioral traits are well-covered.

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?

Two sentences with no redundancy. The primary action is front-loaded, and the caveat and requirement are succinctly appended.

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?

Given the destructive nature and the dependency on knowledge base removal, the description covers the necessary context: action, alternative, and confirmation. No output schema is needed for a delete operation.

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 both 'id' and 'confirm' already described in the input schema. The description adds minimal new meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'delete' and the resource 'uploaded file from Open WebUI', while also specifying the 'permanently' nature. It distinguishes itself from sibling deletion tools by targeting files, and the knowledge base caveat shows scope.

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?

It explicitly instructs when not to use the tool directly ('If the file is in a knowledge base, remove it from the collection first') and names the alternative tool (openwebui_remove_file_from_knowledge). It also states the confirmation prerequisite.

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