github-repo-mcp-server

get_workflow_runs

Check recent GitHub Actions workflow run status (pass/fail) for any repository, with optional branch filtering and result limit.

Instructions

Get recent GitHub Actions workflow run status (pass/fail) for a repo.

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

Input Schema

Name	Required	Description
`repo`	Yes	Repository name
`limit`	No
`owner`	Yes	Repository owner (user or org)
`branch`	No	Filter to runs on this branch

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only mentions 'recent' and 'pass/fail' but does not disclose behavior like default limit, pagination, whether in-progress runs are included, or how branches affect results. This leaves significant ambiguity for an agent.

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?

The description is a single, direct sentence with no filler. It is front-loaded with the action and resource, making it easily scannable.

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?

As a simple getter with no output schema, the description should clarify what is returned. It mentions 'status (pass/fail)' but does not describe the response shape (e.g., list of runs, metadata) or how parameters like limit and branch affect results. It is adequate but could provide more context for an agent.

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 75%, with owner, repo, and branch described. The description adds no new parameter details beyond the schema, and the 'limit' parameter is left unexplained. However, the schema provides defaults and constraints, so the gap is not severe.

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 clearly states the tool retrieves recent GitHub Actions workflow run status (pass/fail) for a repo. It uses a specific verb ('Get') and resource ('workflow run status'), distinguishing it from sibling tools like get_issue or get_file_contents.

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

Usage Guidelines3/5

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

The description implies usage for checking CI status but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. It does not mention prerequisites or typical scenarios, though the purpose is self-evident from the name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server