Skip to main content
Glama

List Automation Runs Tool

list-automation-runs-tool
Read-only

List the runs of one of the user's automations, newest first, 20 per page, however they were started (trigger: manual, schedule or webhook). Each has the same shape as get-automation-run-tool.

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": {
      "automation_id": "<automation_id>"
    },
    "name": "list-automation-runs-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based). Defaults to 1.
automation_idYesThe automation `id` from list-automations-tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: newest-first ordering, a fixed 20-per-page window, and that all trigger origins (manual, schedule, webhook) are included rather than filtered. It stops short of stating pagination termination or total counts.

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?

A single dense sentence with ordering, page size and trigger scope front-loaded, followed by a pointer to the sibling for record shape. No filler, and the fragment about run shape earns its place by avoiding a duplicate schema.

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 compensates by telling the agent each run matches get-automation-run-tool, so return values need not be described. Ordering and page size are covered; the only remaining gap is whether further pages exist or how to detect the last page, which is minor for a 2-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds the missing operational meaning of `page` by disclosing the 20-items-per-page window, which lets an agent reason about offsets. It also clarifies that automation_id must come from list-automations-tool, reinforcing the schema's note.

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 specific verb and resource ('List the runs of one of the user's automations') and scopes it to a single automation, which distinguishes it from get-automation-run-tool (single run) and list-phone-runs-tool (phone runs) by resource. It stops just short of naming a sibling to contrast against, so it lands at a strong 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: you call this to enumerate run history for a known automation, and the required automation_id (sourced from list-automations-tool) is the prerequisite. There is no explicit when-not guidance or named alternative for related queries such as run history of phones, so it is minimum viable rather than instructive.

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