Skip to main content
Glama

List Automation Runs

automation_runs_list
Read-onlyIdempotent

Lists recent runs for one automation: run_id, automation_id, started_at/ended_at, status, retries, trigger_event, and failure_reason. Takes app_id and automation_id (scoped_id or uuid). Optional limit.

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": {
      "app_id": "<app_id>",
      "automation_id": "<automation_id>"
    },
    "name": "automation_runs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many runs to return in one call.
app_idYesThe app this call works on: its `app_id` uuid from `apps_list`.
automation_idYesThe automation scoped_id or uuid returned by `automations_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / app_id / description
      Previous value: -"The app uuid returned by `apps_list`."New value: +"The app this call works on: its `app_id` uuid from `apps_list`."
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of runs to return. Default 20, maximum 100."New value: +"How many runs to return in one call."
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds value by enumerating returned fields (status, retries, trigger_event, failure_reason), which substitutes for a missing output schema, but says nothing about ordering, whether 'recent' is capped by time, or how to page beyond limit.

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 tight sentences: purpose and return shape first, then the parameter summary. Every clause carries information and nothing is padded.

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?

For a simple read-only list tool with no output schema, listing the returned fields plus the identifier formats is nearly enough to call it correctly. Minor gaps remain around the unmentioned organization_id parameter and the absence of any ordering or pagination note.

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 app_id, automation_id, limit, and organization_id are already documented in the schema; the description's note that automation_id accepts a scoped_id or uuid merely repeats that. It omits organization_id entirely, so it adds no meaning beyond the schema, leaving this at the baseline.

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 opens with a specific verb and resource, 'Lists recent runs for one automation', and enumerates the returned fields, which makes it unambiguous that this is the runs-listing tool rather than automation_get or automation_test_run. It stops short of explicitly naming a sibling to distinguish against, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is for inspecting recent run history of an existing automation. There is no explicit when-to-use/when-not guidance, no mention of alternatives such as automation_test_run for triggering a run or automations_metrics_get for aggregate health, and no prerequisites stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources