Skip to main content
Glama

List agent runs

list_agent_runs
Read-only

List the organisation's dispatched AI agent runs across every agent, newest first: run id, agent (task) name, status (pending/running/awaiting_user/completed/failed/cancelled/expired/skipped), what triggered it, when it started and finished, and its outcome summary. Long outcome summaries are clipped here and say so where they were cut - call get_agent_run for the full text. Use this to see what the AI team is doing right now or has done recently. Filter by 'task' (agent name or id) and 'status'. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_agent_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoFilter to one agent: its exact name or task UUID.
limitNoMax runs to return (default 20).
statusNoFilter to one run status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, so the closing 'Read-only' adds nothing, but the description contributes real behavior beyond annotations: newest-first ordering, the full status vocabulary, and the fact that long outcome summaries are clipped with a marker pointing to get_agent_run. It does not mention pagination beyond the limit parameter.

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?

Front-loads what is listed and its ordering, then adds purpose, filtering, and the get_agent_run pointer. Mostly dense and useful, with minor redundancy in the trailing 'Read-only' line that repeats the annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates the returned fields, their ordering, the clipping behavior, and where to get the untruncated text. Combined with the documented filters, an agent has everything needed to call it and interpret the results.

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% and each of the three parameters is already documented, so the baseline is 3. The description restates the 'task' and 'status' filters without adding format or edge-case detail (e.g. what happens when task matches multiple agents) beyond what the schema provides.

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 with explicit scope: lists the organisation's dispatched agent runs across every agent, newest first. It enumerates the returned fields (run id, agent name, status, trigger, timings, outcome summary), which separates it cleanly from get_agent_run and list_agent_tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a concrete usage framing ('see what the AI team is doing right now or has done recently') and names the alternative for full outcome text ('call get_agent_run'). It does not explicitly distinguish itself from the sibling list_agent_tasks, which is a small remaining gap.

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.