Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_automation_runs

Read-onlyIdempotent

Retrieve an automation's recent live and test runs, newest first, with status and skip reasons. Pass a live run ID to test_automation as fromRun to replay it.

Instructions

An automation's recent runs, newest first: live runs (real events) and test runs, with status and why one was skipped. A live run's id can be passed to test_automation as fromRun.

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": "<automation>"
    },
    "name": "list_automation_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many to return, newest first (10 when left out)
automationYesthe automation's id or name

Output Schema

NameRequiredDescriptionDefault
runsYes
automationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral context beyond that: results are newest-first, both live (real events) and test runs are included, and each entry carries status plus a skip reason. It does not discuss volume beyond the limit or any retention window.

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?

A single compact sentence front-loads the resource and ordering, then layers the run-type breakdown and the cross-tool handoff. Dense but every clause carries information; no filler or repetition.

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 an output schema present, the description need not explain return values, and annotations cover safety. Given a two-parameter read tool, the description supplies ordering, run-type coverage, and a workflow link, leaving only minor gaps such as what triggers a skipped run.

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%, with both limit (default 10, max 50, newest first) and automation (id or name) documented inline. The description adds no parameter-level detail beyond what the schema already says, so the baseline of 3 applies.

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 names the resource (an automation's runs) and the scope (recent, newest first, both live and test runs), which is more specific than a restatement of the name. It does not contrast itself with adjacent readers like get_automation, but the cross-reference to test_automation shows the boundary of what a run id is for.

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 rather than stated: an agent learns that live run ids feed test_automation's fromRun, which is a downstream-use hint rather than a when-to-call-this rule. There is no explicit when-not guidance or named alternative for other run-inspection needs.

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