Context Bridge

get_github_actions_runs

Retrieve recent GitHub Actions workflow runs for a repository to check CI status, review outcomes, and troubleshoot failed builds; specify owner, repo, and an optional limit.

Instructions

Retrieves recent GitHub Actions workflow runs for a repository.

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

Input Schema

Name	Required	Description	Default
`repo`	Yes
`limit`	No
`owner`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.7/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 disclosure burden and delivers almost nothing beyond the basic operation. It does not mention authentication requirements, token scopes, rate limits, or pagination behavior, and 'recent' is never quantified. With an output schema present, return shape need not be described, but the operational constraints a caller must anticipate are absent.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though part of that efficiency comes from omitting information rather than from tight writing.

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

Completeness2/5

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

For a three-parameter tool with zero schema description coverage and no annotations, the definition is too thin. The output schema covers return values, but nothing explains the limit default, owner/repo semantics, or auth prerequisites, leaving an agent to guess at call behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. 'For a repository' loosely gestures at owner/repo but never explains their distinction or format, and the limit parameter (default 5) — the key control over result size — is not mentioned at all.

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 names a specific verb ('Retrieves') and a specific resource ('GitHub Actions workflow runs') scoped to a repository. That is enough for an agent to know exactly what comes back. It does not explicitly contrast with siblings, but the siblings listed (Jira, Sentry) are unrelated services, so there is no realistic ambiguity to resolve.

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?

There is no statement of when to use this tool, when not to, or what alternative to pick. The word 'recent' is left undefined — no window, ordering, or recency rule — so an agent cannot judge whether this fits a request for a specific date range or a historical query.

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

Deploy Server