action1-mcp-server

List results

action1_list_instance_endpoint_results

Read-onlyIdempotent

Lists endpoints where a specific automation instance is applied or has run, supporting paging, filtering, sorting, status, and output-format options.

Instructions

List results. Gets a list of endpoints where the automation instance is being applied or has been executed. 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.
`verbose`	No	Skip per-item compactor.
`instance_id`	Yes	Provide a specific instance ID.
`last_status`	No	Specify the last status of the automation instance.
`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: +{
+  "action_name": {},
+  "description": {},
+  "details": {},
+  "endpoint_name": {},
+  "id": {},
+  "percent_completed": {},
+  "self": {},
+  "status": {},
+  "time": {},
+  "type": {}
+}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the permission requirement; it says nothing about pagination behavior, result volume, or what an empty result means, which would have been the value-add beyond structured data.

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?

Two short sentences with no filler and the permission note appended compactly. The only waste is the redundant leading sentence that merely restates the title.

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 so return values need no explanation, and the schema documents all parameters. What's missing is the context an agent actually needs in a 120-tool catalog: how this differs from get_automation_results and list_automation_instances, and whether it lists endpoints or per-endpoint execution records.

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% and all 11 parameters carry their own descriptions (paging, cursor, filter, sortby, verbose, last_status, etc.), so the schema does the heavy lifting. The description adds no parameter meaning at all, making the baseline 3 correct.

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 real work, clarifying that 'results' means the endpoints where an automation instance was applied or executed. But the leading sentence is a tautology of the title, and the definition never distinguishes itself from close siblings such as action1_get_automation_results or action1_list_automation_instances.

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?

It states the required permission (view_automations), which is a useful prerequisite, but gives no guidance on when to choose this over the several automation-result siblings, nor any exclusions. Usage must be inferred entirely.

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

Deploy Server