Skip to main content
Glama

Create Application — Public Repository

coolify_create_application_public

Create an application from a public Git repository, specifying project, server, and build options. Deploy any supported Git provider's public repo with Coolify.

Instructions

Create an application from a public Git repository. You can deploy any kind of public repo from supported Git providers. For Devon's Flavor A apps (Coolify source build).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoApplication display name
revealNoReveal redacted secret values in the response (default false; the call is audited)
domainsNoFQDN for the app (e.g. https://myapp.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_packNoBuild strategynixpacks
git_branchNoGit branch to deploy (default: main)main
descriptionNoApplication description
server_uuidYesUUID of the destination server
project_uuidYesUUID of the target project
ports_exposesNoComma-separated ports to expose (default: 8080)8080
git_repositoryYesFull Git repo URL (e.g. https://github.com/user/repo)
destination_uuidYesUUID of the Docker network/destination on the server
environment_nameNoEnvironment name (default: production)production
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context about source build but does not disclose other behavioral traits such as required permissions, side effects, or limits beyond what annotations provide.

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?

The description is very concise with two sentences, no redundant words. However, it could be slightly expanded to include usage guidance without losing brevity.

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?

Given the number of parameters (13, 5 required) and no output schema, the description is too brief. It does not cover prerequisites, error handling, or what the response contains. More context is needed for the agent to use this tool confidently.

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 baseline is 3. The description does not add any new meaning to parameters beyond the schema. The parameter descriptions in the schema already include detailed information (e.g., for instance).

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 the action (create), resource (application), and source (public Git repository). It also notes the context of Devon's Flavor A apps, which helps distinguish from other create_application variants.

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 mentions 'For Devon's Flavor A apps' but does not explicitly explain when to use this tool versus sibling tools like coolify_create_application_dockerfile or coolify_create_application_githubapp. It lacks guidance on when not to use it.

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