Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-update

Idempotent

Update an existing Dokploy domain's host, port, path, HTTPS, certificate, and routing settings by domain ID to keep deployment access current.

Instructions

POST /domain.update

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": {
      "host": "<host>",
      "domainId": "<domainId>"
    },
    "name": "domain-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
pathNo
portNo
httpsNo
enabledNo
domainIdYes
stripPathNo
domainTypeNo
middlewaresNo
serviceNameNo
internalPathNo
certificateTypeNo
customEntrypointNo
customCertResolverNo
forwardAuthEnabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply idempotentHint=true and openWorldHint=true, but the description adds nothing beyond that: it does not say whether this is a partial or full replacement update, what happens to omitted optional fields, whether the domain must exist, or what is returned. For a 15-parameter mutation this is a total disclosure gap.

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

Conciseness2/5

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

It is short, but brevity here reflects under-specification rather than economy. The single fragment is not front-loaded with any actionable information an agent could act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 15-parameter mutation with zero schema descriptions, no output schema, and only minimal annotations needs a substantial description to be usable. The route-string-only description leaves an agent unable to call this correctly except by guessing from parameter names.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, so the description carries the full burden of explaining them. It mentions none — no meaning for host, path, stripPath, certificateType, middlewares, customEntrypoint, or any other field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only "POST /domain.update" — an HTTP route restating the tool name. It implies a domain mutation but never states what is being updated or how it differs from siblings such as domain-toggleEnable, domain-generateDomain, or domain-create.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, no prerequisites, and no mention of alternatives — despite many sibling tools operating on domains (domain-toggleEnable, domain-delete, domain-one) where disambiguation matters.

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