Skip to main content
Glama

GitHub list workflow runs

github_list_workflow_runs
Read-only

List recent GitHub Actions workflow runs for a repository. Prefer the exact owner from github_list_repositories; 'repo' also accepts the combined 'owner/name' form. Returns run status, conclusion, branch, triggering event, and links. Use this to check if CI/CD pipelines are passing, find failed builds, or monitor deployment workflows.

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": {
      "repo": "<repo>"
    },
    "name": "github_list_workflow_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name. Also accepts the combined 'owner/name' form.
limitNoMaximum number of runs to return (max 15).
ownerNoRepository owner (e.g. 'octocat'). Prefer the exact owner from a prior github_list_repositories call. May be omitted when the repository name is unambiguous in this organisation, or embedded in 'repo' as 'owner/name'.
branchNoFilter runs by branch name.
statusNoFilter by status: 'completed', 'in_progress', 'queued', 'requested', 'waiting', 'pending', or by conclusion: 'success', 'failure', 'cancelled', 'neutral', 'skipped', 'stale', 'timed_out', 'action_required'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint already tells the agent this is a safe read, so the description's added value is the return-shape disclosure: status, conclusion, branch, triggering event, and links. That matters because there is no output schema. It stops short of describing ordering ('recent') precisely or noting that the limit is capped by the schema.

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?

Three tight sentences lead with the purpose, then the required-parameter convention, then the return fields and use cases. Nothing is wasted, though the owner/repo guidance partially repeats what the schema description already says.

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 read-only, single-resource list tool with full schema coverage and no output schema, the definition covers purpose, prerequisites, return fields, and use cases adequately. Minor gaps remain around how many runs are considered 'recent' and how this differs from the per-run jobs sibling.

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 coverage is 100%, so all five parameters including the status enum are already documented in structured form, making 3 the baseline. The description restates the 'owner/name' convention for repo and the preference for an exact owner, which largely duplicates the schema rather than adding new meaning.

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 pairs a specific verb with a specific resource ('List recent GitHub Actions workflow runs for a repository'), so an agent immediately knows the object being queried. It does not distinguish itself from close siblings such as github_get_workflow_run_jobs or list_application_workflow_runs, leaving the agent to infer which lister applies.

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?

It gives concrete when-to-use triggers: check if CI/CD pipelines are passing, find failed builds, or monitor deployments. It also names github_list_repositories as the source of the owner value. There are no explicit exclusions or pointers to the sibling tools that fetch jobs for a run, so the boundary between this and github_get_workflow_run_jobs is left implicit.

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.