Skip to main content
Glama
euisuh

Nginx Proxy Manager MCP

by euisuh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Proxy Host

update_proxy_host

Update writable settings on an existing proxy host by ID to change routing or options. Preview changes with dry_run=True without affecting NPM.

Instructions

Update writable settings on an existing proxy host by ID. Use this to change routing or options; use enable_proxy_host or disable_proxy_host for status only. NPM receives the merged writable host fields, without requesting a certificate. Returns the updated host object with its ID and current settings. Set dry_run=True to preview the exact request without changing NPM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the proxy host, from the matching list tool.
dry_runNoWhen True, return the exact request preview without changing NPM.
ssl_forcedNoWhether NPM redirects HTTP requests to HTTPS. For updates, omit to keep the current value.
domain_namesNoDomain names routed by this host or certificate. For updates, omit to keep the current value.
forward_hostNoUpstream hostname or IP address. For updates, omit to keep the current value.
forward_portNoUpstream TCP port number. For updates, omit to keep the current value.
access_list_idNoNPM access-list ID to attach. Omit to keep the current value.
block_exploitsNoWhether NPM enables its exploit-blocking option. For updates, omit to keep the current value.
certificate_idNoNPM certificate ID to attach. Omit to keep the current value.
forward_schemeNoUpstream scheme: http or https. For updates, omit to keep the current value.
caching_enabledNoWhether NPM enables proxy caching. For updates, omit to keep the current value.
allow_websocket_upgradeNoWhether NPM allows WebSocket upgrades. For updates, omit to keep the current value.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.5.2
    • addedInput schema / properties / access_list_id / description
      Added value: +"NPM access-list ID to attach. Omit to keep the current value."
    • addedInput schema / properties / allow_websocket_upgrade / description
      Added value: +"Whether NPM allows WebSocket upgrades. For updates, omit to keep the current value."
    • addedInput schema / properties / block_exploits / description
      Added value: +"Whether NPM enables its exploit-blocking option. For updates, omit to keep the current value."
    • addedInput schema / properties / caching_enabled / description
      Added value: +"Whether NPM enables proxy caching. For updates, omit to keep the current value."
    • addedInput schema / properties / certificate_id / description
      Added value: +"NPM certificate ID to attach. Omit to keep the current value."
    • addedInput schema / properties / domain_names / description
      Added value: +"Domain names routed by this host or certificate. For updates, omit to keep the current value."
    • addedInput schema / properties / dry_run / description
      Added value: +"When True, return the exact request preview without changing NPM."
    • addedInput schema / properties / forward_host / description
      Added value: +"Upstream hostname or IP address. For updates, omit to keep the current value."
    • addedInput schema / properties / forward_port / description
      Added value: +"Upstream TCP port number. For updates, omit to keep the current value."
    • addedInput schema / properties / forward_scheme / description
      Added value: +"Upstream scheme: http or https. For updates, omit to keep the current value."
    • addedInput schema / properties / id / description
      Added value: +"ID of the proxy host, from the matching list tool."
    • addedInput schema / properties / ssl_forced / description
      Added value: +"Whether NPM redirects HTTP requests to HTTPS. For updates, omit to keep the current value."
  2. First observedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden well: it explains that NPM receives merged writable fields (partial-update semantics), that no certificate is requested, and that the updated host object is returned. It does not cover permission/auth requirements or whether the change is reversible, which is the only remaining 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?

Four tight sentences, front-loaded with the verb+resource, then the alternative routing, then behavioral facts. No filler and nothing repeated.

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?

All 12 parameters are documented in the schema, an output schema exists so return values need not be explained, and the description adds the key merged-update and no-cert behaviors. Only auth/permission prerequisites are absent, which is minor for this tool size.

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% and each parameter already documents 'omit to keep the current value', so the baseline is 3. The description reinforces the merge semantics with 'merged writable host fields' and highlights dry_run, but adds no syntax or format detail beyond the schema.

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, resource, and scoping ('Update writable settings on an existing proxy host by ID'), and explicitly distinguishes itself from the enable/disable siblings. An agent can route to the correct tool without opening any 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?

Gives explicit when-to-use ('change routing or options') versus when-not ('status only' -> enable_proxy_host/disable_proxy_host), and names the alternatives directly. The dry_run preview hint adds a further condition for safe invocation.

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