Skip to main content
Glama

GitHub get workflow run jobs

github_get_workflow_run_jobs
Read-only

Get the jobs and step-level details for a specific GitHub Actions workflow run. Prefer the exact owner from github_list_repositories; 'repo' also accepts the combined 'owner/name' form. Returns each job's status, conclusion, timing, and individual step results. Use this after listing workflow runs to drill into a specific run and see which step failed.

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>",
      "run_id": "<run_id>"
    },
    "name": "github_get_workflow_run_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name. Also accepts the combined 'owner/name' form.
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'.
run_idYesThe workflow run ID. Get this from github_list_workflow_runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds useful behavioral context: it states the response includes job status, conclusion, timing, and individual step results, which matters since there is no output schema. It omits pagination and rate-limit behavior, keeping it short of a 5.

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?

Four short sentences with the core action front-loaded and the parameter hints and usage note following in logical order. Slight redundancy between the description's owner/name note and the schema's identical wording costs it a point.

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 getter with three well-documented parameters and no output schema, the description covers what the tool returns (job and step detail) plus how to obtain its inputs. Absent output-schema detail on pagination or result caps is the only remaining gap.

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%, so all three parameters are already documented. The description largely restates that guidance (exact owner from github_list_repositories, 'owner/name' form accepted, run_id from github_list_workflow_runs), reinforcing provenance but adding no syntax or constraints beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and resource ('Get the jobs and step-level details') and scopes it to 'a specific GitHub Actions workflow run', which cleanly separates it from sibling readers like github_list_workflow_runs or github_get_job_logs.

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 explicit sequencing guidance ('Use this after listing workflow runs to drill into a specific run and see which step failed'), which tells the agent both when to call it and what question it answers. It does not explicitly contrast with github_get_job_logs or get_application_workflow_run_jobs, so the boundary with those siblings 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.