Skip to main content
Glama
bunkerity

BunkerWeb MCP

Official
by bunkerity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

configs_delete_bulk

Destructive

Deletes multiple BunkerWeb custom config snippets in one call by service, type, and name, reducing repeated single deletions; changes are saved to the database for later scheduler application.

Instructions

Delete several custom config snippets in one call. Use config_delete for one. Saved to the database; the scheduler applies it later; this tool cannot confirm it is live.

Input Schema

NameRequiredDescriptionDefault
configsYesSnippets to delete, each by service, type and name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • changedInput schema / $defs / ConfigKeyParams / properties / name / description
      Previous value: -"Configuration name"New value: +"Snippet name: letters, digits, _ or -, no extension"
    • changedInput schema / $defs / ConfigKeyParams / properties / service / description
      Previous value: -"Service identifier or global"New value: +"Service ID that owns the snippet; omit or 'global' for global"
    • changedInput schema / $defs / ConfigKeyParams / properties / type / description
      Previous value: -"Configuration type"New value: +"Custom config type, e.g. http, server-http, default-server-http, stream, server-stream, modsec, modsec-crs, crs-plugins-before, crs-plugins-after"
    • addedInput schema / properties / configs / description
      Added value: +"Snippets to delete, each by service, type and name"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the delete is persisted to the database and only applied later by the scheduler, and that the tool cannot confirm the change is live. This is exactly the asynchronous caveat an agent needs before reporting success. It stops short of saying whether deletion is reversible or what happens if a listed snippet does not exist.

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, zero waste, with the scope stated first and the caveat last. Every sentence carries distinct information.

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?

No output schema exists, so the description correctly signals that no liveness confirmation is returned, which is the key completeness concern for a destructive bulk call. What remains unaddressed is partial-failure semantics for a batch delete, a meaningful gap for an array-input destructive tool.

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 the nested ConfigKeyParams fields (name, type, service) are fully documented inline, so the description adds little parameter detail. It frames the input as a list of snippets keyed by service/type/name, but does not state behavior for duplicate or unknown entries. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource with an explicit bulk scope ('Delete several custom config snippets in one call'), which distinguishes it from the singular sibling config_delete by name. An agent can tell exactly what it does without opening the schema.

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 routes the agent: bulk use here, single deletion via config_delete. The alternative and the condition that selects it are both named, leaving nothing to inference.

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