action1-mcp-server

Create a automation schedule

action1_create_automation_schedule

Destructive

Creates a scheduled automation to run actions like deploying updates or executing scripts on specified endpoints at a defined time.

Instructions

Create a automation schedule. Schedules a new automation. The automation will be executed against a specified list of endpoints. 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.

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.

Changed20 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"
+  }
+}

addedInput schema / properties / body / required

Added value: +[
+  "name",
+  "retry_minutes",
+  "actions",
+  "settings"
+]

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

A3.5/5.0

Behavior3/5

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

Annotations already disclose non-readOnly, destructive, non-idempotent, and open-world behavior. The description adds an important authorization requirement, 'Perm: manage_automations', and endpoint execution scope, but it does not elaborate on destructive effects or the confirm/dry-run safeguards beyond what the schema already documents.

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?

The description is short and front-loaded with the core action. The first two sentences are slightly redundant, but overall it is efficient and wastes little space.

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?

With a full input schema, an output schema, and rich annotations, the description does not need to explain return values or parameter details. It supplies the permission requirement and endpoint scope, though it still leaves schedule-vs-instance routing implicit for a complex destructive creation tool.

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%, so the input schema already documents the parameters in detail. The description only echoes endpoint targeting and permission, adding little semantic meaning beyond the structured schema.

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 uses a specific verb, 'Create', and resource, 'automation schedule', and adds that the automation runs against a specified endpoint list plus the required permission. It is clear on its own, but it does not explicitly distinguish this tool from siblings such as action1_create_automation_instance or action1_update_automation.

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?

The description states the required permission and that execution targets endpoints, which gives useful usage context. However, it does not say when to choose this schedule-creation tool over alternatives like creating an automation instance or updating an existing automation, nor does it provide exclusions.

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

Deploy Server