action1-mcp-server

Poll an automation until it terminates

action1_wait_for_automation

Read-onlyIdempotent

Wait for an Action1 automation instance to reach a terminal status—Stopped, Success, Warning, or Error—or time out. Use it to poll script runs and optionally fetch filtered output.

Instructions

Block until an automation instance reaches a terminal status (Stopped/Success/Warning/Error) or timeout.

Input Schema

Name	Required	Description
`org_id`	No	Org UUID.
`endpoint_id`	No	If set, also fetch filtered script output.
`instance_id`	Yes	Instance UUID.
`response_format`	No	Output format. Default markdown.
`timeout_seconds`	No	Polling timeout.
`poll_interval_seconds`	No	Poll interval seconds.

Output Schema

Name	Required	Description	Default
`output`	No	string
`status`	No	object

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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"

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 / output

Added value: +{
+  "description": "string"
+}

addedOutput schema / properties / status

Added value: +{
+  "description": "object"
+}

First observedv0.5.0Jun 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description successfully adds value by specifying the exact terminal statuses (Stopped/Success/Warning/Error) that define termination, giving the agent crucial behavioral context regarding the expected exit states.

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?

The description is a single, dense, and efficient sentence. It front-loads the core behavior (Block until) and the condition (terminal status/timeout) with zero waste.

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

Completeness5/5

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

Given the detailed input schema and annotations, the description provides all necessary context to perform the core function correctly—namely, initiating a blocking wait operation and understanding its termination conditions.

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?

The schema description coverage is 100%, meaning the structured data already defines all parameters (like UUID types or poll intervals). The description adds no semantic meaning beyond what the schema provides.

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?

The tool description is extremely precise, stating it blocks until an automation instance reaches a terminal state. This explicitly differentiates it from 'get status' or 'get results' tools in the sibling list.

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?

The title and description clearly dictate the use case: when the user needs to actively wait for an asynchronous operation to finish. While it doesn't explicitly list all alternatives, the defined blocking nature makes the required usage intuitive.

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

Deploy Server