Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Deploy

coolify_deploy
Destructive

Trigger deployments by tag name or resource UUID, and deploy multiple comma-separated resources at once through MCP Hub to release updates.

Instructions

[UNIFIED] Trigger deployment by tag name or resource UUID. Can deploy multiple resources at once using comma-separated values.

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>"
    },
    "name": "coolify_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
prNo
tagNo
siteYes
uuidNo
forceNo
docker_tagNo
pull_request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare this a non-read-only, non-idempotent, destructive operation, so the description is not required to restate the safety profile. It does add genuine behavioral context by disclosing batch deployment via comma-separated selectors, but it omits whether deployment is asynchronous, what `force` overrides, and what happens to the currently running containers.

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, front-loaded with the action and selector model, with no filler. The only waste is the unexplained "[UNIFIED]" tag, and the brevity comes at the cost of under-specification rather than verbosity.

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?

For a destructive, non-idempotent batch mutation with 7 undocumented parameters and no output schema, the description is far too thin. An agent cannot determine what `site` is for, what the tool returns, or how to confirm success.

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 7 parameters, so the description must carry the load and it does not. It only clarifies the `tag`/`uuid` selector semantics and comma-separated batching, leaving the required `site` parameter plus `pr`, `pull_request_id`, `docker_tag`, and `force` 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?

"Trigger deployment by tag name or resource UUID" gives a specific verb (trigger/deploy) and a clear selector model, which separates it from siblings like coolify_cancel_deployment or coolify_get_deployment. The "[UNIFIED]" prefix and the unexplained required `site` parameter keep it from being fully unambiguous.

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?

There is no statement of when to use this versus coolify_cancel_deployment or coolify_get_deployment, no prerequisites, and no warning about re-deploying an already-running resource. The only guidance offered — comma-separated values for multiple resources — is a capability statement, not a when-to-use rule.

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