MCP Hub

Overview Schema Source Related Servers Discussions Admin

Coolify: Create application docker image

coolify_create_application_docker_image

Destructive

Create a Coolify application from a Docker image by providing the project, server, environment, image name, and exposed ports.

Instructions

[UNIFIED] Create a Coolify application from a Docker image. Requires project_uuid, server_uuid, environment, docker_registry_image_name, and ports_exposes.

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": {
      "site": "<site>",
      "project_uuid": "<project_uuid>",
      "server_uuid": "<server_uuid>",
      "environment_name": "<environment_name>",
      "docker_registry_image_name": "<docker_registry_image_name>",
      "ports_exposes": "<ports_exposes>"
    },
    "name": "coolify_create_application_docker_image"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`site`	Yes
`domains`	No
`description`	No
`server_uuid`	Yes
`project_uuid`	Yes
`ports_exposes`	Yes
`instant_deploy`	No
`destination_uuid`	No
`environment_name`	Yes
`docker_registry_image_tag`	No
`docker_registry_image_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.14.0Nov 12, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the description should add what actually happens — whether a deployment is triggered, what instant_deploy controls, or what is destroyed on failure. It adds none of that, and its required-parameter list even omits 'site', which the schema marks required.

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?

Two tight sentences with the resource and prerequisites front-loaded and no filler. Brevity here reflects under-specification rather than bloat, but the structure itself is clean.

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

Completeness2/5

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

A destructive 12-parameter mutation with no output schema and zero schema documentation needs far more than a required-field recap. Key behaviors — deployment triggering, registry tag defaults, whether creation is reversible — are absent.

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 12 parameters, so the description carries full burden, yet it names only 5 (and calls one 'environment' where the schema says environment_name), leaving name, domains, description, site, destination_uuid, instant_deploy, and docker_registry_image_tag completely undocumented.

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

Purpose4/5

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

States a specific verb and resource: create a Coolify application from a Docker image. This distinguishes it from the compose/dockerfile/private_github_app/public creation siblings by naming the source type, though it never names those alternatives explicitly.

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

Usage Guidelines2/5

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

The second sentence lists a subset of required inputs but gives no guidance on when to choose a Docker-image application over a compose, Dockerfile, or public-repo application, and no preconditions (project/server must exist, registry auth needed). The agent must infer selection from the tool name alone.

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

Deploy Server