Skip to main content
Glama
onemarc

GitHub Actions MCP Server

by onemarc

get_workflow_run

Retrieve detailed information about a specific GitHub Actions workflow run by providing the repository owner, repository name, and run ID for effective monitoring and analysis.

Instructions

Get details of a specific workflow run

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner
repoYesRepository name
runIdYesThe ID of the workflow run

Implementation Reference

  • The main handler function for the 'get_workflow_run' tool. It extracts owner, repo, and runId from args, calls the GitHub Octokit API to get the workflow run details, returns the data, or throws a WorkflowError on failure.
    const handleGetWorkflowRun: ToolHandler = async (args, octokit: Octokit) => {
      const { owner, repo, runId } = args;
      
      try {
        const response = await octokit.rest.actions.getWorkflowRun({
          owner,
          repo,
          run_id: runId
        });
    
        return response.data;
      } catch (error: any) {
        throw new WorkflowError(`Failed to get workflow run: ${error.message}`, error.response?.data);
      }
    };
    
    export default handleGetWorkflowRun;
  • The tool definition including name, description, and input schema for validating arguments: owner, repo, runId.
    {
      name: "get_workflow_run",
      description: "Get details of a specific workflow run",
      inputSchema: {
        type: "object",
        properties: {
          owner: { type: "string", description: "Repository owner" },
          repo: { type: "string", description: "Repository name" },
          runId: { type: "number", description: "The ID of the workflow run" }
        },
        required: ["owner", "repo", "runId"]
      }
    },
  • Registration of the 'get_workflow_run' handler in the toolHandlers object, mapped to handleGetWorkflowRun imported from './get-workflow-run.js'.
    export const toolHandlers: Record<string, ToolHandler> = {
      create_workflow: handleCreateWorkflow,
      list_workflows: handleListWorkflows,
      get_workflow: handleGetWorkflow,
      get_workflow_usage: handleGetWorkflowUsage,
      list_workflow_runs: handleListWorkflowRuns,
      get_workflow_run: handleGetWorkflowRun,
      get_workflow_run_jobs: handleGetWorkflowRunJobs,
      trigger_workflow: handleTriggerWorkflow,
      cancel_workflow_run: handleCancelWorkflowRun,
      rerun_workflow: handleRerunWorkflow,
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets details' but doesn't specify what details are returned (e.g., status, logs, duration), whether it's a read-only operation, or any error conditions. This leaves significant gaps in understanding the tool's behavior beyond basic retrieval.

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, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly, which is ideal for clarity in tool selection.

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?

Given the complexity of workflow runs (which can involve statuses, logs, artifacts, etc.), no annotations, and no output schema, the description is insufficient. It doesn't explain what details are returned, potential errors, or how it differs from sibling tools, leaving the agent with incomplete context for effective use.

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?

The input schema has 100% description coverage, clearly documenting all three required parameters (owner, repo, runId). The description adds no additional meaning beyond what the schema provides, such as explaining relationships between parameters or usage examples, so it meets the baseline for high schema coverage.

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 clearly states the verb ('Get details') and resource ('specific workflow run'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_workflow' or 'list_workflow_runs', which would require more specificity about what details are retrieved versus those other tools.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_workflow' (for workflow metadata) or 'list_workflow_runs' (for multiple runs). It lacks context about prerequisites, such as needing a specific run ID, or exclusions, leaving the agent to infer usage from the name alone.

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

Related 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/onemarc/github-actions-mcp-server'

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