Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Automation Runs

list-automation-runs
Read-onlyIdempotent

Retrieve an automation's runs newest first, one per contact entry, with status, current step, and failure reason; filter by status or contact and paginate results.

Instructions

List the runs of an automation, newest first: one per contact entry, with its status, the step it is on and why it failed. Don't read ids or timestamps back to the user unless they ask for them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "list-automation-runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe automation id.
afterNoCursor for the next page: the `id` of the last item on this page. Cannot be combined with `before`.
limitNoItems per page, 1-100. Defaults to 20.
beforeNoCursor for the previous page: the `id` of the first item on this page.
statusNoOnly runs in these statuses, comma-separated: `running`, `waiting`, `completed`, `failed`, `cancelled`.
contact_idNoOnly the runs of this contact, from list-contacts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower; the description still adds real value by describing what each row contains (status, current step, failure reason) in the absence of an output schema, plus the newest-first ordering. It omits pagination behavior and total counts, which keeps it from a 5.

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 sentences, no filler, with the core purpose and ordering front-loaded and the output-shaping advice delegated to a short trailing sentence.

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?

With no output schema, the description responsibly sketches the row shape and ordering, and pagination is fully covered by the schema. It is nearly complete for a list tool; only the interaction between filters and paging (e.g. that contact_id narrows to a single contact's runs) goes unstated.

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 the schema already documents id, cursors, limit, status and contact_id, including the mutually-exclusive after/before constraint. The description adds nothing parameter-level beyond the phrase 'one per contact entry', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the runs of an automation'), the ordering ('newest first'), and the return granularity ('one per contact entry') with the fields surfaced (status, current step, failure reason). This makes it distinguishable from the singular get-automation-run and from list-automations without reading either schema.

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 never says when to choose this over get-automation-run or list-automations, nor any prerequisites (e.g. the automation must exist). The only guidance present is a presentation rule about not echoing ids/timestamps, which does not help an agent select the tool.

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

Deploy Server

Other Tools