openwebui-mcp-server

openwebui_delete_prompt

Delete a saved prompt by specifying its command and confirming deletion. Use this tool to remove unwanted prompts from Open WebUI.

Instructions

Delete a saved prompt by its command. 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": {
      "command": "<command>",
      "confirm": "<confirm>"
    },
    "name": "openwebui_delete_prompt"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	Prompt command to delete (e.g. "/summarize")
`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.0

Behavior3/5

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

The description discloses the destructive nature via the verb 'delete' and adds a key behavioral requirement (confirm must be true). However, with no annotations provided, it doesn't mention irreversibility, permissions, or side effects, leaving a partial transparency gap.

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?

A single, front-loaded sentence contains the essential information with no filler.

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 two-parameter delete tool with no output schema, the description provides the necessary action, identification method, and confirmation requirement. It could be more explicit about permanence, but overall it's adequate.

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%, and both parameters have descriptions. The description adds minimal new meaning beyond the schema, only reinforcing that the tool selects by 'command' and requires 'confirm true'.

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 uses the specific verb 'Delete', identifies the resource ('saved prompt'), and specifies the targeting mechanism ('by its command'). This clearly distinguishes it from sibling delete tools for chats, files, functions, etc.

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 states a clear prerequisite: 'Requires confirm: true', which tells the agent how to invoke the tool safely. It doesn't explicitly mention alternatives or exclusions, but for a delete operation, the context is clear.

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