Skip to main content
Glama
Sign In
BunkerWeb MCP

BunkerWeb MCP

Official
by bunkerity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_service

Destructive

Change a BunkerWeb service's settings, rename it, or set draft/published status; unknown or externally owned keys are skipped and stored values are read back.

Instructions

Change a service's settings, rename it or set is_draft; needs MULTISITE=yes. Unknown or externally owned keys are skipped, and a receipt reads back the stored values. Use update_global_config for global. Saved to the database; the scheduler applies it later; this tool cannot confirm it is live.

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": {
      "service": "<service>"
    },
    "name": "update_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesExisting service identifier
is_draftNoTrue makes the service an unpublished draft, false publishes it
variablesNoUnprefixed per-service setting names and values; unknown or externally owned names are skipped and reported.
server_nameNoRename the service

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • changedInput schema / properties / is_draft / description
      Previous value: -"Toggle draft state"New value: +"True makes the service an unpublished draft, false publishes it"
  2. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / is_draft / description
      Added value: +"Toggle draft state"
    • addedInput schema / properties / server_name / description
      Added value: +"Rename the service"
    • addedInput schema / properties / service / description
      Added value: +"Existing service identifier"
    • addedInput schema / properties / variables / description
      Added value: +"Unprefixed per-service setting names and values; unknown or externally owned names are skipped and reported."
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: unknown or externally owned keys are skipped rather than erroring, a receipt reads back stored values, the change is persisted to the database, and the scheduler applies it asynchronously so the tool cannot confirm it is live. That asynchronous/eventual-consistency warning is exactly the kind of context annotations cannot convey. It stops short of saying whether omitted parameters are preserved or cleared, which matters for a destructiveHint=true mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and resource, then constraints and caveats, with no filler sentences. It reads slightly telegraphic ('needs MULTISITE=yes' dropped mid-clause) but every clause carries information an agent needs.

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 mutation tool with no output schema, it covers the prerequisite (MULTISITE), skip semantics, persistence/async behavior, and the return receipt. The remaining gap is partial-update semantics and failure modes, but the essentials for calling it correctly are present.

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 description coverage is 100%, so the baseline is 3: the schema already explains service, is_draft, variables (including the skip-and-report behavior), and server_name as rename. The description mostly restates those mappings in compressed form rather than adding new semantics such as value formats or conflict resolution.

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 plus resource and enumerates the three capability modes it covers (change settings, rename, set is_draft). It explicitly contrasts itself with update_global_config, so the agent can separate it from the nearest sibling without opening either schema.

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?

Names the alternative (update_global_config for global settings) and gives a concrete prerequisite: MULTISITE=yes. It does not spell out when to use create_service vs. this tool, but the mutation-on-existing-surface is strongly implied by 'Existing service identifier' and 'Change a service's settings'.

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