Skip to main content
Glama
onemarc

GitHub Actions MCP Server

by onemarc
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

rerun_workflow

Re-run a GitHub Actions workflow by specifying the repository owner, name, and workflow run ID, enabling quick retries and error resolution.

Instructions

Re-run a workflow run

Input Schema

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

Implementation Reference

  • src/tools/tool-definitions.ts:173-185 (schema)
    Input schema definition for the 'rerun_workflow' tool.
    {
  name: "rerun_workflow",
  description: "Re-run a 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"]
  }
}
  • src/tools/index.ts:24-24 (registration)
    Maps the 'rerun_workflow' tool name to its handler function in the toolHandlers export.
    rerun_workflow: handleRerunWorkflow,
  • src/tools/index.ts:12-12 (registration)
    Import statement for the 'rerun_workflow' handler function.
    import handleRerunWorkflow from './rerun-workflow.js';

Tool Definition Quality

C2.9/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 of behavioral disclosure. 'Re-run' implies a mutation operation, but the description doesn't specify permissions required, side effects (e.g., if it cancels the current run), rate limits, or what happens on success/failure. This leaves significant gaps for a tool that modifies workflow state.

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 with zero wasted words. It's appropriately sized for a simple tool and front-loaded with the core action. Every word earns its place, making it easy to parse quickly.

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 a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 're-run' entails behaviorally, what the expected outcome is, or how it differs from similar operations. For a tool that likely has significant side effects, more context is needed to guide proper usage.

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 description coverage is 100%, with clear documentation for 'owner', 'repo', and 'runId' parameters. The description adds no additional parameter semantics beyond what's in the schema. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even without param info in the description.

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 'Re-run a workflow run' clearly states the action (re-run) and resource (workflow run) with a specific verb. However, it doesn't distinguish this from sibling tools like 'trigger_workflow' or 'create_workflow', which might have overlapping functionality. The purpose is clear but lacks sibling differentiation.

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. It doesn't mention prerequisites (e.g., needing an existing workflow run), exclusions, or comparisons to siblings like 'trigger_workflow' or 'cancel_workflow_run'. Without any usage context, the agent must infer when this tool is appropriate.

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