Skip to main content
Returns one workflow run with its jobs and, for failed jobs, the names of the failed steps. Use github_get_job_logs with a job id to read why it failed.

​
Authentication and enablement

Requires a connected native GitHub integration (mcp:github) — a first-party GitHub App connection, not Composio. The connector is shown on Trail and to Nanonets superadmins; it is hidden from Nanonets customers during rollout. Connecting opens GitHub’s install page for the Trail GitHub App, where the user picks the account and either all repositories or only selected ones. Tools act as the app’s bot account through short-lived installation tokens — not as the connecting user — and reach only the repositories of that installation. To change which repositories are included, edit the installation on GitHub (the account’s or organization’s installed GitHub Apps settings) or reconnect. If an organization owner still has to approve the app, calls fail until they do; if the app was uninstalled or suspended, calls fail until GitHub is reconnected. Relies on the app’s Actions (read) permission.

​
Inputs

  • owner (required): repository owner (user or organization).
  • repo (required): repository name.
  • run_id (required): workflow run id (from github_list_workflow_runs).

​
Output

  • run: id, workflow name, triggering event, status, conclusion, branch, commit SHA, URL, and created/updated times.
  • jobs: id, name, status, conclusion, URL, and failed_steps (names of steps that failed or timed out) per job.

​
Limits and side effects

  • Read-only.
  • owner/repo must be plain GitHub names (letters, numbers, ., _, -); anything else is rejected before any API call.
  • run_id must be a positive integer.
  • Returns the first 100 jobs of the run’s latest attempt.

​
Expected errors

  • No GitHub connection, a connection still waiting for an organization owner to approve the app, or an app that was uninstalled or suspended (reconnect GitHub).
  • Invalid owner/repo format.
  • run_id missing or not a positive integer.
  • GitHub API errors surface as the tool’s error, rewritten to say what to fix: not found or no access to that repository (404 — check which repositories the installation includes), the repository is empty (no commits yet, HTTP 409), rate limit reached with the retry time (including GitHub’s secondary limits, which ask for a one-minute wait), rejected app credentials (reconnect).