Skip to main content
Glama

Coolify: Create application private github app

coolify_create_application_private_github_app
Destructive

Create a Coolify application from a private GitHub repository by linking an existing Coolify GitHub App. Provide the GitHub App UUID or source UUID alias to deploy the repository.

Instructions

[UNIFIED] Create a Coolify application from a private GitHub repository using an already configured Coolify GitHub App. Use github_app_uuid, or source_uuid as a backwards-compatible alias.

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>",
      "git_repository": "<git_repository>",
      "git_branch": "<git_branch>",
      "build_pack": "<build_pack>",
      "ports_exposes": "<ports_exposes>"
    },
    "name": "coolify_create_application_private_github_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
siteYes
domainsNo
build_packYes
git_branchYes
descriptionNo
server_uuidYes
source_uuidNo
project_uuidYes
ports_exposesYes
git_repositoryYes
instant_deployNo
github_app_uuidNo
environment_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=true and idempotent=false, so the safety profile is covered by structured data. The description adds the meaningful prerequisite that a GitHub App must already be configured, but says nothing about what is created, whether a deployment is triggered, or how instant_deploy changes outcomes.

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 short sentences with the distinguishing scope front-loaded and no filler. The '[UNIFIED]' prefix is a tag with no informational value for an agent and is the only real waste.

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 14-parameter creation tool with no output schema and no parameter documentation needs far more than a one-line purpose plus an alias note. An agent could identify the tool but not confidently supply build_pack, ports_exposes, environment_name or instant_deploy.

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

Parameters2/5

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

Schema description coverage is 0% across 14 parameters, so the description carries the full explanatory burden and largely does not meet it. It usefully clarifies the github_app_uuid/source_uuid alias relationship, but leaves build_pack, ports_exposes, environment_name, instant_deploy, domains and the remaining fields entirely unexplained.

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 an application) and scopes it to a private GitHub repository backed by an already configured Coolify GitHub App, which implicitly separates it from the public/dockerfile/compose variants. It stops short of naming the sibling it complements or contrasts with, so differentiation is inferential rather than explicit.

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 phrase 'using an already configured Coolify GitHub App' implies a prerequisite, and the second sentence tells the agent how to choose between github_app_uuid and source_uuid. There is no explicit when-to-use vs when-not, and nothing routing the agent to the public-repo or dockerfile/compose variants when those fit better.

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