Skip to main content
Glama

Create private GitHub App application

createPrivateGithubAppApplication

Create a new application using a private GitHub App to deploy from a private repository. Specify project, server, environment, GitHub app, repository, branch, build pack, and ports.

Instructions

Create a new application using a private GitHub App. Requires project_uuid, server_uuid, environment_name (or environment_uuid), github_app_uuid, git_repository, git_branch, build_pack, and ports_exposes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
domainsNo
redirectNo
is_staticNo
build_packYes
dockerfileNo
git_branchYes
descriptionNo
limits_cpusNo
server_uuidYes
watch_pathsNo
project_uuidYes
static_imageNo
build_commandNo
custom_labelsNo
limits_cpusetNo
limits_memoryNo
ports_exposesYes
start_commandNo
base_directoryNo
git_commit_shaNo
git_repositoryYes
instant_deployNo
ports_mappingsNo
github_app_uuidYes
install_commandNo
destination_uuidNo
environment_nameYes
environment_uuidYes
use_build_serverNo
health_check_hostNo
health_check_pathNo
health_check_portNo
limits_cpu_sharesNo
publish_directoryNo
docker_compose_rawNo
limits_memory_swapNo
autogenerate_domainNo
health_check_methodNo
health_check_schemeNo
health_check_enabledNo
health_check_retriesNo
health_check_timeoutNo
force_domain_overrideNo
health_check_intervalNo
docker_compose_domainsNo
pre_deployment_commandNo
docker_compose_locationNo
post_deployment_commandNo
health_check_return_codeNo
http_basic_auth_passwordNo
http_basic_auth_usernameNo
limits_memory_swappinessNo
connect_to_docker_networkNo
custom_docker_run_optionsNo
docker_registry_image_tagNo
health_check_start_periodNo
limits_memory_reservationNo
docker_registry_image_nameNo
health_check_response_textNo
is_http_basic_auth_enabledNo
manual_webhook_secret_giteaNo
manual_webhook_secret_githubNo
manual_webhook_secret_gitlabNo
manual_webhook_secret_bitbucketNo
pre_deployment_command_containerNo
post_deployment_command_containerNo
docker_compose_custom_build_commandNo
docker_compose_custom_start_commandNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says what the tool does (creates) and what is required, but does not mention side effects, permissions, return values, or whether deployment is triggered. This is a significant gap for a write operation.

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 a single sentence that is concise and free of fluff, beginning with the core purpose. However, it becomes a list-like run-on and could be better structured by separating the purpose from the requirements.

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?

This tool has 69 parameters and no output schema, making it highly complex. The description only covers the basic purpose and a subset of required fields, offering no information about optional parameters, return values, or error scenarios. It is far from complete for an agent to successfully invoke this tool.

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?

With 0% schema description coverage, the description must compensate by explaining parameter meanings. It lists the required parameters but does not define them or explain their roles. For instance, it mentions 'build_pack' and 'ports_exposes' but does not clarify their values or purpose. The only added semantic is the 'or' between environment_name and environment_uuid, indicating they are alternatives.

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') and the resource ('a new application') and specifies the mechanism ('using a private GitHub App'), distinguishing it from sibling tools like createPrivateDeployKeyApplication and createPublicApplication. The purpose is immediately understandable.

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 when to use this tool by mentioning 'private GitHub App' but does not explicitly contrast with alternatives or provide exclusion criteria. It lists required parameters, which gives some context, but no explicit guidance on choosing this over similar create application tools.

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/frndchagas/coolify-mcp'

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