Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-update

Idempotent

Update an existing Dokploy application's configuration, including build, source, environment, and deployment settings, by providing its application ID and the fields to change.

Instructions

POST /application.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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
argsNo
iconNo
nameNo
ownerNo
titleNo
branchNo
appNameNo
commandNo
enabledNo
giteaIdNo
cpuLimitNo
githubIdNo
gitlabIdNo
passwordNo
replicasNo
subtitleNo
usernameNo
buildArgsNo
buildPathNo
buildTypeNo
createdAtNo
modeSwarmNo
autoDeployNo
cleanCacheNo
dockerfileNo
giteaOwnerNo
networkIdsNo
previewEnvNo
registryIdNo
repositoryNo
sourceTypeNo
watchPathsNo
bitbucketIdNo
descriptionNo
dockerImageNo
giteaBranchNo
gitlabOwnerNo
isStaticSpaNo
labelsSwarmNo
memoryLimitNo
previewPathNo
previewPortNo
registryUrlNo
triggerTypeNo
buildSecretsNo
customGitUrlNo
gitlabBranchNo
networkSwarmNo
previewHttpsNo
previewLimitNo
refreshTokenNo
ulimitsSwarmNo
applicationIdYes
buildServerIdNo
createEnvFileNo
dropBuildPathNo
environmentIdNo
herokuVersionNo
previewLabelsNo
bitbucketOwnerNo
cpuReservationNo
giteaBuildPathNo
placementSwarmNo
rollbackActiveNo
bitbucketBranchNo
buildRegistryIdNo
customGitBranchNo
giteaRepositoryNo
gitlabBuildPathNo
gitlabProjectIdNo
previewWildcardNo
railpackVersionNo
dockerBuildStageNo
enableSubmodulesNo
gitlabRepositoryNo
healthCheckSwarmNo
previewBuildArgsNo
publishDirectoryNo
applicationStatusNo
customGitSSHKeyIdNo
dockerContextPathNo
endpointSpecSwarmNo
memoryReservationNo
updateConfigSwarmNo
bitbucketBuildPathNo
customGitBuildPathNo
restartPolicySwarmNo
rollbackRegistryIdNo
bitbucketRepositoryNo
gitlabPathNamespaceNo
previewBuildSecretsNo
rollbackConfigSwarmNo
detachDokployNetworkNo
stopGracePeriodSwarmNo
previewCertificateTypeNo
bitbucketRepositorySlugNo
previewCustomCertResolverNo
isPreviewDeploymentsActiveNo
previewRequireCollaboratorPermissionsNo

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 only declare openWorldHint=true and idempotentHint=true; the description adds nothing beyond them. For a write operation with 100 parameters there is no disclosure of partial-vs-full update semantics, side effects (e.g. triggering a redeploy), permission requirements, or what gets overwritten when optional fields are omitted.

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?

The single line is short but that brevity is under-specification rather than efficiency; there is no structure, no front-loaded purpose, and nothing an agent can act on. It is technically free of filler but also free of information.

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?

Given a 100-parameter mutation with no output schema, no schema descriptions, and minimal annotations, the description is nowhere near adequate. An agent cannot safely call this tool without guessing at field semantics and update behavior.

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 100 parameters, so the description carries the entire burden and provides zero parameter meaning. Critical distinctions such as the four enums (buildType, sourceType, triggerType, applicationStatus), the modeSwarm/placementSwarm nested objects, and whether nullable fields mean "unset" or "leave unchanged" are left completely unexplained.

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?

"POST /application.update" only restates the tool name as an HTTP endpoint. It names a verb and resource but says nothing about what an application update entails, which fields are meaningful, or how it differs from siblings like application-move or application-saveBuildType.

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 when-to-use guidance, no prerequisites, and no routing to alternatives among the many sibling tools that also mutate application state. An agent has no basis for choosing this over application-create, application-redeploy, or the provider-specific save tools.

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