Skip to main content
Glama

Update Coolify Application

coolify_update_application
Idempotent

Update an application's configuration, including name, domains, Git settings, build pack, health checks, and ports. Only supply fields to change.

Instructions

Update an application's configuration. Supports changing name, description, domains, Git settings, build pack, health check config, ports, and more. Only supply the fields you want to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew application name
uuidYesThe UUID of the resource
revealNoReveal redacted secret values in the response (default false; the call is audited)
domainsNoNew FQDN (e.g. https://app.devonwatkins.com)
instanceYesREQUIRED — which Coolify instance to mutate: 'prod' (Hetzner VPS) or 'dev' (local OrbStack VM). No default: state the target explicitly so a write never lands on prod by accident.
build_packNoNew build strategy
git_branchNoNew Git branch
descriptionNoNew description
custom_labelsNoCustom Traefik labels (set to empty string to reset/auto-generate)
ports_exposesNoNew exposed ports
git_repositoryNoNew Git repo URL
private_key_uuidNoUUID of Coolify private key to link for Git access
health_check_pathNoHealth check endpoint path
health_check_portNoHealth check port
health_check_enabledNoEnable/disable health checks
docker_compose_domainsNoService-to-domain mapping for compose apps
docker_compose_locationNoPath to compose file in the repo (e.g. /docker-compose.yml)
docker_registry_image_tagNoNew Docker image tag
health_check_start_periodNoHealth check start period in seconds (e.g. 15)
docker_registry_image_nameNoNew Docker image name
Behavior3/5

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

Annotations (idempotentHint=true, destructiveHint=false) already indicate safety; the description adds no contradictions but also no additional context beyond the update action.

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?

Extremely concise: one sentence stating purpose, followed by a clear usage instruction. No filler.

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

Completeness3/5

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

With 20 parameters and no output schema, the description covers changeable fields but does not explain return values or side effects (e.g., whether update triggers a deployment).

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 main description adds only a summary. It does not add new meaning beyond what the schema provides.

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?

The description clearly states it updates an application's configuration, lists categories of fields (name, domains, Git settings, etc.), and distinguishes from sibling tools for creation, deletion, etc.

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

Usage Guidelines3/5

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

The description implies incremental updates via 'Only supply the fields you want to change' but does not explicitly state when to use this tool versus creating or deploying, nor any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlobarQuest/infraops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server