action1-mcp-server

Get automation script output (filtered)

action1_get_automation_output

Read-onlyIdempotent

Retrieves filtered stdout for a single endpoint in an automation instance and removes Action1 status markers, making automation results readable.

Instructions

Returns filtered stdout for one endpoint of an automation instance. Strips Action1 status markers.

Input Schema

Name	Required	Description
`org_id`	No	Org UUID.
`endpoint_id`	Yes	Endpoint UUID.
`include_raw`	No	If true, also include raw description list.
`instance_id`	Yes	Instance UUID.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description
`raw`	No	array
`output`	No	string
`skipped_status_lines`	No	number

Schema Changelog

Changes observed during successful MCP inspections.

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

changedInput schema / properties / endpoint_id / pattern

Previous value: -"^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"New value: +"^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"

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

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

addedOutput schema / properties / skipped_status_lines
```
Added value: +{
+  "description": "number"
+}
```

First observedv0.5.0Jun 27, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral detail beyond annotations by saying the stdout is filtered and that Action1 status markers are stripped.

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 two short sentences with no wasted wording. The core return behavior is front-loaded and the marker-stripping behavior follows immediately.

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?

Given the output schema exists and annotations cover safety, the description provides enough context about what is returned: filtered stdout for a specific endpoint of an automation instance. The main remaining gap is sibling differentiation, which is a usage-guideline concern rather than a missing return-value explanation.

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 all five parameters are already documented by the schema. The description only loosely maps 'one endpoint' and 'automation instance' to the required parameters and does not add meaningful semantics for include_raw, response_format, or org_id.

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 and resource: returns filtered stdout for one endpoint of an automation instance. It also adds that Action1 status markers are stripped, but it does not explicitly distinguish this tool from related siblings such as get_automation_script_output or get_automation_results.

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 description implies the tool is used to retrieve per-endpoint automation output, but it gives no explicit guidance on when to choose it over related output/result/status tools. There are many similar automation siblings, and no alternative is named.

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

Deploy Server