action1-mcp-server

List recent automation instances

action1_list_recent_automations

Read-onlyIdempotent

Lists recent automation instances for an organization with pagination and optional JSON or markdown output. Use it to inspect recent runs; use action1_automations_summary for counts.

Instructions

List recent automation instances for the org. For counts use action1_automations_summary instead.

Input Schema

Name	Required	Description
`limit`	No	Max items.
`cursor`	No	Pagination cursor.
`org_id`	No	Org UUID.
`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.

Changed4 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 / items / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

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 declare this as a safe, read-only, idempotent listing operation, so the safety profile is covered. The description adds only org scoping and a vague recency qualifier; it doesn't state the recency window, pagination behavior, or any limits beyond what the schema already provides.

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?

Two short sentences with zero filler; the core operation is front-loaded and the alternative tool routing follows immediately. Nothing is wasted.

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?

The output schema and annotations carry much of the behavioral burden, and the schema fully documents the parameters. The key missing piece is disambiguation from action1_list_automation_instances and a definition of 'recent', which matter for correct tool selection.

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 four parameters (limit, cursor, org_id, response_format) are already documented in the schema. The description contributes no additional parameter meaning beyond implying org scoping, so the baseline of 3 applies.

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 gives a clear verb and resource (list recent automation instances) and scopes it to the org, so the agent knows the general operation. It does not, however, distinguish this tool from the very similarly named sibling action1_list_automation_instances, which makes the exact purpose of 'recent' ambiguous.

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?

It explicitly routes count-oriented requests to action1_automations_summary, which is a useful alternative. But it gives no guidance on when to use this over action1_list_automation_instances, nor does it define what qualifies as 'recent', leaving usage partly inferred.

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

Deploy Server