action1-mcp-server

Update a automation schedule

action1_update_automation

Destructive

Update an existing automation schedule by changing its actions, endpoint targets, timing, and retry settings, with dry-run preview or confirmed execution.

Instructions

Update a automation schedule. Perm: manage_automations.

Input Schema

Name	Required	Description
`body`	Yes	Request body (schema: AutomationSchedulePayload)
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`automation_id`	Yes	Provide a specific automation ID.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`tool`	No
`type`	No
`actions`	No
`dry_run`	No
`last_run`	No
`next_run`	No
`settings`	No
`endpoints`	No
`would_send`	No
`last_instance`	No
`retry_minutes`	No
`settings_timezone`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / body / properties

Added value: +{
+  "actions": {
+    "description": "One automation can contain multiple actions.",
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "params": {
+              "additionalProperties": {},
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "template_id": {
+              "const": "deploy_update",
+              "type": "string"
+            }
+          },
+          "required": [
+            "template_id",
+            "name",
+            "params"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "params": {
+              "additionalProperties": {},
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "template_id": {
+              "const": "deploy_package",
+              "type": "string"
+            }
+          },
+          "required": [
+            "template_id",
+            "name",
+            "params"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "params": {
+              "additionalProperties": {},
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "template_id": {
+              "const": "uninstall_program",
+              "type": "string"
+            }
+          },
+          "required": [
+            "template_id",
+            "name",
+            "params"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "params": {
+              "additionalProperties": {},
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "template_id": {
+              "const": "run_script",
+              "type": "string"
+            }
+          },
+          "required": [
+            "template_id",
+            "name",
+            "params"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "params": {
+              "additionalProperties": {},
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "template_id": {
+              "const": "reboot",
+              "type": "string"
+            }
+          },
+          "required": [
+            "template_id",
+            "name",
+            "params"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "params": {
+              "additionalProperties": {},
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "template_id": {
+              "const": "update_ring",
+              "type": "string"
+            }
+          },
+          "required": [
+            "template_id",
+            "name",
+            "params"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  "endpoints": {
+    "description": "IDs of endpoints and/or groups to run this batch on.",
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "name": {
+    "description": "The automation name.",
+    "type": "string"
+  },
+  "retry_minutes": {
+    "description": "The number of minutes to keep trying to run on disconnected/powered off endpoints.",
+    "type": "string"
+  },
+  "settings": {
+    "description": "### Available schedule settings: - ONCE - apply only once on a specified DATE and AT a...",
+    "type": "string"
+  },
+  "settings_timezone": {
+    "description": "The time zone for automation execution: - UTC - the automation will execute at the same...",
+    "enum": [
+      "UTC",
+      "LOCALTIME"
+    ],
+    "type": "string"
+  }
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
addedOutput schema / properties / actions
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / endpoints
```
Added value: +{}
```
addedOutput schema / properties / id
```
Added value: +{}
```
addedOutput schema / properties / last_instance
```
Added value: +{}
```
addedOutput schema / properties / last_run
```
Added value: +{}
```
addedOutput schema / properties / name
```
Added value: +{}
```
addedOutput schema / properties / next_run
```
Added value: +{}
```
addedOutput schema / properties / retry_minutes
```
Added value: +{}
```
addedOutput schema / properties / self
```
Added value: +{}
```
addedOutput schema / properties / settings
```
Added value: +{}
```
addedOutput schema / properties / settings_timezone
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / type
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the danger profile is known without the description. The description does add the required permission scope (manage_automations), which is genuinely useful context, but it never says whether the update replaces the whole schedule payload or merges, nor that confirm="YES" plus dry_run=false are needed to actually execute.

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, front-loaded sentences with no filler. The brevity is efficient rather than padded, though the second sentence is a bare permission tag rather than useful prose.

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

Completeness3/5

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

With an output schema, rich annotations and full schema coverage, much of the burden is carried elsewhere. Still, for a destructive, non-idempotent update with a nested payload and an explicit confirm gate, the description should at minimum signal replacement semantics and the dry-run default.

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 description coverage is 100%, including per-field docs for body, settings, endpoints, retry_minutes, confirm and dry_run, so the baseline is 3. The description adds no parameter semantics of its own — no explanation of automation_id scope or of the settings/endpoints payload shape.

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?

States a specific verb+resource ('Update a automation schedule'), and the name separates it from create/get/list schedule siblings by the verb alone. It does not explicitly distinguish it from action1_update_automation-adjacent tools such as create_automation_schedule or get_automation_schedule, so an agent gets the gist but no sibling routing.

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?

The only extra sentence is 'Perm: manage_automations.', which is an authorization requirement, not usage guidance. Nothing says when to update versus create a new schedule, whether the schedule should be fetched first, or how confirm/dry_run govern execution.

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

Deploy Server