Skip to main content
Glama

create_github_app

Create a new GitHub App configuration to integrate with Coolify for deploying and managing applications. Specify name and optionally organization, enterprise URLs, or custom settings.

Instructions

Create a new GitHub App configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGitHub App name
organizationNoGitHub organization (optional)
api_urlNoGitHub API URL (for GitHub Enterprise)
html_urlNoGitHub HTML URL (for GitHub Enterprise)
custom_userNoCustom Git user
custom_portNoCustom Git port
is_system_wideNoMake available system-wide

Implementation Reference

  • Tool schema definition for 'create_github_app' — defines its name, description, and input properties (name required; organization, api_url, html_url, custom_user, custom_port, is_system_wide optional).
      name: 'create_github_app',
      description: 'Create a new GitHub App configuration',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'GitHub App name' },
          organization: { type: 'string', description: 'GitHub organization (optional)' },
          api_url: { type: 'string', description: 'GitHub API URL (for GitHub Enterprise)' },
          html_url: { type: 'string', description: 'GitHub HTML URL (for GitHub Enterprise)' },
          custom_user: { type: 'string', description: 'Custom Git user' },
          custom_port: { type: 'number', description: 'Custom Git port' },
          is_system_wide: { type: 'boolean', description: 'Make available system-wide', default: false }
        },
        required: ['name']
      }
    },
  • Handler implementation for 'create_github_app' — validates that 'name' is provided and makes a POST request to the '/github-apps' endpoint with all provided arguments.
    case 'create_github_app':
      requireParam(args, 'name');
      return client.post('/github-apps', args);
Behavior2/5

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

No annotations provided, so description carries full burden. It fails to disclose behavioral traits such as authentication requirements, idempotency, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no fluff, but lacks structure and critical information for a 7-parameter tool.

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?

No output schema, no annotations, and many sibling tools. Description provides no context on return values, side effects, or differentiation.

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 coverage is 100% with individual parameter descriptions. Description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Description states 'Create a new GitHub App configuration', which is a clear verb+resource. However, it does not differentiate from sibling tools like 'create_private_github_app_application'.

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?

No guidance on when to use this tool versus alternatives, no context on prerequisites or when-not-to-use.

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

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