openwebui-mcp-server

openwebui_delete_function

Delete a function from Open WebUI permanently. Provide the function ID and confirm to remove it.

Instructions

Delete a function from Open WebUI. This removes the function permanently. 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_function"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Function 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.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that deletion is permanent and requires confirm: true, which are critical behavioral aspects. It does not mention side effects or authorization, but for a simple delete, this is adequate.

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?

The description is two sentences, begins with the core purpose, and includes essential details without excess. Every sentence adds 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?

The tool is simple with two required parameters and no output schema. The description covers purpose, permanence, and confirmation requirement, which is sufficient for an agent to understand the tool's behavior.

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?

The input schema already provides full descriptions for both parameters (id and confirm). The description adds the note that confirm must be true, which reinforces the schema, but does not add new meaning beyond that. With 100% schema coverage, the baseline is 3.

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 'Delete a function from Open WebUI' with a specific verb and resource, distinguishing it from sibling delete tools for chats, files, and prompts.

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

Usage Guidelines4/5

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

The description provides clear context for deleting functions and notes the required confirm flag, which implies the usage. It does not explicitly compare to alternatives, but the resource scope is unambiguous given the tool name and sibling set.

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