Skip to main content
Glama

List workflow runs

list_runs
Read-only

Recent workflow runs, newest first (limit 1-200), optionally for one workflow slug.

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_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
projectNo
workflowNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond the annotations by disclosing sort order ('newest first') and the accepted limit range (1-200). It says nothing about pagination, cursors, or how many results come back by default beyond the schema's default of 20.

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 front-loaded line with no filler; the resource and ordering come first, with the limit and filter constraints following. Nothing here could be removed without losing information.

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

Completeness3/5

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

An output schema exists so return values need not be explained, and annotations cover the read-only nature. However, for a three-parameter tool with zero schema descriptions, the unexplained project parameter and the absence of pagination behavior leave the definition short of complete.

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 0%, so the description has to carry parameter meaning; it does explain the limit bounds (1-200) and that workflow takes a single slug. The third parameter, project, is never mentioned, and no formats or examples are given for the slug value.

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?

States the specific resource (workflow runs) and the ordering ('newest first'), so an agent knows it is a listing operation over runs rather than a single-record fetch like get_run. It does not distinguish itself from the sibling list_recent_jobs, which sounds like a near-equivalent listing tool.

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 phrase 'optionally for one workflow slug' hints at when to pass the filter, but there is no explicit when-to-use guidance, no mention of when to prefer get_run for a specific run, and no note about the sibling list_recent_jobs.

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