action1-mcp-server

List automation instances

action1_list_automation_instances

Read-onlyIdempotent

List running and completed automation instances for an organization, with filters for status, completion, endpoint, and pagination to review automation results.

Instructions

List automation instances. Gets a list of running and completed automations for the specified organization. Perm: view_automations.

Input Schema

Name	Required	Description
`from`	No	Provide the number of the first record to be returned.
`limit`	No	Set the maximum number of items to be returned (the page size).
`cursor`	No	next_cursor of the previous call; takes precedence over from.
`filter`	No	Provide a case-insensitive substring to filter and narrow down returned results (i.e., if...
`org_id`	No	Org UUID.
`sortby`	No	Define the sorting order by a certain field.
`status`	No	Specify the status.
`verbose`	No	Skip per-item compactor.
`completed`	No	Specify the completion status of the automation schedule.
`endpoint_id`	No	The ID of the endpoint to query.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 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 / auto_paginate / description

Previous value: -"Walk all pages."New value: +"Walk pages until limit or the size budget; then continue with next_cursor."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor."New value: +"next_cursor of the previous call; takes precedence over from."

addedInput schema / properties / from / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / from / minimum
```
Added value: +0
```
addedInput schema / properties / limit / maximum
```
Added value: +50000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

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 / items / items / properties

Added value: +{
+  "actions": {},
+  "end_time": {},
+  "endpoint_results": {},
+  "endpoints": {},
+  "id": {},
+  "name": {},
+  "percent_completed": {},
+  "retry_minutes": {},
+  "schedule": {},
+  "self": {},
+  "start_time": {},
+  "status": {},
+  "type": {}
+}

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?

Annotations already declare this read-only, idempotent, and non-destructive, so the safety profile doesn't need restating. The description adds a real behavioral fact, the view_automations permission requirement, but leaves the pagination model (cursor vs. from, auto_paginate) entirely to the schema.

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 with the purpose front-loaded and no irrelevant filler. There is mild redundancy between 'List automation instances' and 'Gets a list of...', which keeps it from being maximally tight.

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?

Rich structured context (full schema coverage, four annotations, an output schema) means the description needn't explain return values. However, for a 12-parameter list tool with many overlapping siblings, the missing routing guidance to list_recent_automations or get_automation_instance is a notable gap.

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 12 parameters including cursor precedence and the status/completed enums are already documented. The description merely implies org scoping via 'the specified organization' and adds no format, default, or interaction details beyond the schema, so baseline 3 is appropriate.

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 and resource ('List automation instances') and adds the scope ('running and completed automations for the specified organization'). That scope phrase meaningfully separates it from list-type siblings like action1_list_recent_automations, but the definition never names or explicitly contrasts those siblings.

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 guidance is the required permission ('Perm: view_automations'). With siblings such as action1_list_recent_automations, action1_get_automation_instance, and action1_list_automation_schedules in the catalog, an agent gets no signal about when to pick this tool over those alternatives.

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

Deploy Server