coolify-mcp

get_deployments

List active deployments or retrieve deployment history for a specific application by UUID, with pagination.

Instructions

List active deployments (no args) or the deployment history for a specific application (app_uuid). Supports pagination with skip/take.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deployments"
  }
}

Input Schema

Name	Required	Description
`skip`	No	Number of records to skip (pagination). Only used with app_uuid.
`take`	No	Number of records to return (pagination). Only used with app_uuid.
`app_uuid`	No	Application UUID whose deployment history to retrieve. Omit for all active deployments.
`instance`	No	Coolify instance name (omit for the default).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It discloses the two operational modes and pagination support. It doesn't explicitly state read-only status, but 'List' implies it. Slight ambiguity about pagination applying only to history mode is resolved by schema.

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

Conciseness5/5

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

Two sentences, front-loaded with the main action, no wasted words. Perfectly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core behaviors and parameter usage. It doesn't describe return format, but for a list tool without output schema, this is acceptable. The tool is adequately scoped for selection and invocation.

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

Parameters4/5

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

Schema already documents all parameters (100% coverage). The description adds the semantic distinction that app_uuid toggles modes and skip/take are pagination controls, which is valuable beyond the schema.

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?

Clear verb 'List' with specific resource 'deployments', and distinguishes two modes: active deployments (no args) or history for a specific app (app_uuid). This differentiates it from siblings like list_resources and get_logs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context on when to use each mode and pagination parameters. However, it doesn't explicitly mention alternatives or when not to use this tool, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.