Skip to main content
Glama
ko1ynnky

GitHub Actions MCP Server

by ko1ynnky

list_workflow_runs

Retrieve GitHub Actions workflow runs by filtering criteria like status, branch, or actor to monitor execution history and analyze performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
workflowIdNoThe ID of the workflow or filename (string or number)
actorNoReturns someone's workflow runs. Use the login for the user
branchNoReturns workflow runs associated with a branch
eventNoReturns workflow runs triggered by the event
statusNoReturns workflow runs with the check run status
createdNoReturns workflow runs created within date range (YYYY-MM-DD)
excludePullRequestsNoIf true, pull requests are omitted from the response
checkSuiteIdNoReturns workflow runs with the check_suite_id
pageNoPage number for pagination
perPageNoResults per page (max 100)

Implementation Reference

  • The main handler function that executes the tool logic: validates inputs, constructs GitHub API URL, fetches workflow runs, and parses response using WorkflowRunsSchema.
    export async function listWorkflowRuns(
      owner: string, 
      repo: string, 
      options: {
        workflowId?: string | number,
        actor?: string,
        branch?: string,
        event?: string,
        status?: string,
        created?: string,
        excludePullRequests?: boolean,
        checkSuiteId?: number,
        page?: number,
        perPage?: number
      } = {}
    ) {
      owner = validateOwnerName(owner);
      repo = validateRepositoryName(repo);
    
      let url;
      if (options.workflowId) {
        url = `https://api.github.com/repos/${owner}/${repo}/actions/workflows/${options.workflowId}/runs`;
      } else {
        url = `https://api.github.com/repos/${owner}/${repo}/actions/runs`;
      }
    
      url = buildUrl(url, {
        actor: options.actor,
        branch: options.branch,
        event: options.event,
        status: options.status,
        created: options.created,
        exclude_pull_requests: options.excludePullRequests ? "true" : undefined,
        check_suite_id: options.checkSuiteId,
        page: options.page,
        per_page: options.perPage
      });
    
      const response = await githubRequest(url);
      return WorkflowRunsSchema.parse(response);
    }
  • Zod schema defining input parameters and validation for the list_workflow_runs tool.
    export const ListWorkflowRunsSchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      workflowId: z.string().optional().describe("The ID of the workflow or filename (string or number)"),
      actor: z.string().optional().describe("Returns someone's workflow runs. Use the login for the user"),
      branch: z.string().optional().describe("Returns workflow runs associated with a branch"),
      event: z.string().optional().describe("Returns workflow runs triggered by the event"),
      status: z.enum(['completed', 'action_required', 'cancelled', 'failure', 'neutral', 'skipped', 'stale', 'success', 'timed_out', 'in_progress', 'queued', 'requested', 'waiting', 'pending']).optional().describe("Returns workflow runs with the check run status"),
      created: z.string().optional().describe("Returns workflow runs created within date range (YYYY-MM-DD)"),
      excludePullRequests: z.boolean().optional().describe("If true, pull requests are omitted from the response"),
      checkSuiteId: z.number().optional().describe("Returns workflow runs with the check_suite_id"),
      page: z.number().optional().describe("Page number for pagination"),
      perPage: z.number().optional().describe("Results per page (max 100)"),
    });
  • src/index.ts:177-185 (registration)
    MCP server tool registration for 'list_workflow_runs', providing schema and wrapper handler that delegates to the main implementation.
    server.tool(
        "list_workflow_runs",
        actions.ListWorkflowRunsSchema.shape,
        async (request: any) => {
            const { owner, repo, workflowId, ...options } = request;
            const result = await actions.listWorkflowRuns(owner, repo, { workflowId, ...options });
            return { content: [{ type: "text", text: JSON.stringify(result) }] };
        }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ko1ynnky/github-actions-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server