action1-mcp-server

Get a specific instance

action1_get_automation_instance

Read-onlyIdempotent

Retrieves details for a specific automation instance by automation ID, enabling you to inspect its status and configuration.

Instructions

Get a specific instance. Gets details about a automation instance specified by its ID. Perm: view_automations.

Input Schema

Name	Required	Description
`org_id`	No	Org UUID.
`verbose`	No	Skip per-item compactor.
`automation_id`	Yes	Provide a specific automation ID.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`type`	No
`status`	No
`actions`	No
`end_time`	No
`schedule`	No
`endpoints`	No
`start_time`	No
`retry_minutes`	No
`endpoint_results`	No
`percent_completed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 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 / actions
```
Added value: +{}
```
- addedOutput schema / properties / end_time
```
Added value: +{}
```
- addedOutput schema / properties / endpoint_results
```
Added value: +{}
```
- addedOutput schema / properties / endpoints
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / percent_completed
```
Added value: +{}
```
- addedOutput schema / properties / retry_minutes
```
Added value: +{}
```
- addedOutput schema / properties / schedule
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / start_time
```
Added value: +{}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description needn't restate safety. It usefully adds the required scope (view_automations), but says nothing about what "details" comprise, how org scoping affects the lookup, or what happens if the ID is from another org.

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?

Three short sentences, front-loaded with the action. The first sentence is pure redundancy with the title and wastes space, but overall the text is compact and free of padding.

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?

An output schema exists and annotations cover the safety profile, so return values need not be explained. Still, for a lookup tool sitting among many similarly named automation-result tools, the description leaves the agent without a clear basis for choosing it or understanding scoping behavior.

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 schema already documents all four parameters, and the description only echoes automation_id. It adds no meaning for org_id, verbose ("Skip per-item compactor" is opaque and would have benefited from elaboration), or response_format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The second sentence does give a specific verb and resource ("Gets details about a automation instance specified by its ID"), but the first sentence merely restates the tool name. No differentiation from close siblings such as action1_get_automation_status, action1_get_automation_results, or action1_get_automation_script_output, all of which also retrieve data for an automation instance.

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?

There is no guidance on when to pick this tool over action1_get_automation_status / results / output / list_automation_instances. The only extra clause, "Perm: view_automations," is a permission prerequisite rather than a usage rule.

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

Deploy Server