coolify-mcp

Overview Schema Source Related Servers Discussions Admin

coolify_update_database_backup

Update a database backup schedule's configuration, including frequency, retention, and storage settings, to adjust when and how backups are taken.

Instructions

[WRITE] Update a database backup schedule configuration

Input Schema

TableJSON Schema

Name	Required	Description
`uuid`	Yes	UUID of the database
`enabled`	No
`save_s3`	No
`timeout`	No
`dump_all`	No
`frequency`	No	Cron expression for the backup schedule
`backup_uuid`	Yes	UUID of the scheduled backup
`custom_fields`	No	Additional fields not listed above (advanced)
`s3_storage_uuid`	No	S3 storage UUID (required with save_s3)
`databases_to_backup`	No
`missing_backup_notification_days`	No	Alert after this many days without an execution; 0 disables alerts (Coolify v4.3.23)
`database_backup_retention_days_s3`	No
`database_backup_retention_amount_s3`	No
`database_backup_retention_days_locally`	No
`database_backup_retention_amount_locally`	No
`database_backup_retention_max_storage_s3`	No
`database_backup_retention_max_storage_locally`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv4.1.0Sep 25, 2026

addedInput schema / properties / database_backup_retention_amount_locally

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / database_backup_retention_amount_s3

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / database_backup_retention_days_locally

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / database_backup_retention_days_s3

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / database_backup_retention_max_storage_locally
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / database_backup_retention_max_storage_s3
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```

removedInput schema / properties / database_name_prefix

Removed value: -{
-  "description": "Prefix for backup database name",
-  "type": "string"
-}

addedInput schema / properties / databases_to_backup

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / dump_all
```
Added value: +{
+  "type": "boolean"
+}
```

removedInput schema / properties / enabled / description

Removed value: -"Enable or disable the backup schedule"

changedInput schema / properties / frequency / description

Previous value: -"Cron frequency for backups"New value: +"Cron expression for the backup schedule"

addedInput schema / properties / frequency / minLength
```
Added value: +1
```

addedInput schema / properties / missing_backup_notification_days

Added value: +{
+  "description": "Alert after this many days without an execution; 0 disables alerts (Coolify v4.3.23)",
+  "maximum": 365,
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / s3_storage_id

Removed value: -{
-  "description": "S3 storage ID for remote backups",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}

addedInput schema / properties / s3_storage_uuid

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "S3 storage UUID (required with save_s3)"
+}

addedInput schema / properties / save_s3
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / timeout

Added value: +{
+  "maximum": 36000,
+  "minimum": 60,
+  "type": "integer"
+}

First observedv4.0.0Aug 18, 2026

TDQS

C2.7/5.0

Behavior2/5

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

The '[WRITE]' prefix signals mutation, but no annotations are provided and the description does not disclose whether the update is partial or full, whether unspecified optional parameters are reset, or what side effects occur. With zero annotation coverage, the description carries the full burden and only minimally addresses it.

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?

The description is a single front-loaded sentence with no wasted words. However, for a tool with 17 parameters and no annotations, this brevity borders on under-specification rather than effective conciseness.

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

Completeness1/5

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

With 17 parameters, only 35% schema description coverage, no annotations, and no output schema, a one-sentence description is grossly incomplete. It lacks update semantics, parameter interaction guidance, and any expectation of the response or error behavior.

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 only 35%, so the description needed to compensate, but it names no parameters and adds no meaning beyond 'schedule configuration.' It does not explain key relationships such as s3_storage_uuid being required when save_s3 is true, nor clarify any of the many optional fields.

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?

The description states a specific verb ('Update') and a specific resource ('database backup schedule configuration'), which distinguishes it from create/delete/list backup tools. It could more explicitly contrast with coolify_update_database, but the resource is clearly the backup schedule, not the database itself.

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?

Usage is implied by the verb 'Update' — the agent can infer this is for modifying an existing backup schedule. However, there is no explicit guidance on when to prefer this over create/delete/list backup tools, nor any mention of prerequisites such as the backup already existing.

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

Deploy Server

coolify_update_database_backup

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools