action1-mcp-server

List automation schedules

action1_list_automation_schedules

Read-onlyIdempotent

List existing scheduled automations and narrow results by substring, organization, pagination, or sorting parameters.

Instructions

List automation schedules. Lists existing scheduled automations. Use parameters to filter out automations in the returned. 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.
`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": {},
+  "endpoints": {},
+  "id": {},
+  "last_instance": {},
+  "last_run": {},
+  "name": {},
+  "next_run": {},
+  "retry_minutes": {},
+  "self": {},
+  "settings": {},
+  "settings_timezone": {},
+  "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 define this as a read-only, idempotent, and safe operation. The description adds valuable contextual information by specifying the required permission ('Perm: view_automations'), which is not covered by the standard hints.

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?

The description is highly concise and front-loads the core function and the operational necessity (parameter use). Each short sentence serves a distinct and necessary purpose.

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?

Given the complexity of the 9 parameters, the description is minimally complete. It relies heavily on the schema for structural details, which is adequate for a listing tool but lacks full behavioral context regarding scope or boundaries.

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?

Since the schema coverage is 100%, the description provides no additional semantic value for the parameters, which adhere to the baseline score of 3.

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 purpose is clearly stated in the title and first sentence: it lists existing scheduled automations. Although it is specific, it does not contrast itself with very similar list tools in the sibling list, resulting in a 4 instead of a 5.

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 only provides a high-level tip that parameters should be used to filter the results. It fails to provide guidance on when this tool should be used versus alternatives like listing recent automations or fetching a specific schedule.

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

Deploy Server