GitHub Actions MCP Server

github_rollback_deployment

Roll back a GitHub environment to an earlier ref by creating a new deployment for that ref and marking the current deployment inactive.

Instructions

Roll back to a previous deployment by creating a new deployment pointing to a specific ref and marking the current deployment as inactive.

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>",
      "environment": "<environment>",
      "ref": "<ref>"
    },
    "name": "github_rollback_deployment"
  }
}

Input Schema

Name	Required	Description
`ref`	Yes	The git ref (commit SHA, branch, or tag) to deploy
`repo`	Yes	Repository name
`owner`	Yes	Repository owner
`environment`	Yes	Environment to roll back (e.g. 'production')
`currentDeploymentId`	No	ID of the current deployment to mark as inactive

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the core behavior (creating a new deployment and marking the current one inactive), which is more than just stating 'rollback'. However, it does not explain side effects like whether the operation triggers workflows, requires special permissions, or is irreversible, and it leaves ambiguous whether marking inactive only happens when currentDeploymentId is supplied.

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, well-structured sentence that conveys the essential action without fluff. It earns its place completely, with no redundant information.

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?

Despite full schema parameter descriptions and clear purpose, the description is incomplete for a mutation tool without annotations. It does not clarify the role of the optional currentDeploymentId (whether marking inactive is conditional), how to obtain that ID, what the API returns, or whether the action is asynchronous. More context is needed to safely invoke the tool effectively.

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%, so baseline is 3. The description adds minimal extra meaning beyond the schema, only referencing 'specific ref' and 'current deployment' which map to ref and currentDeploymentId. It does not enrich the parameter understanding beyond what the schema already provides.

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's function: rolling back a deployment by creating a new deployment to a specific ref and marking the current one inactive. This is a specific verb+resource combination that distinguishes it from sibling tools like github_get_deployments which only lists deployments.

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 the tool is used for rolling back deployments, but it does not provide explicit guidance on when to use it versus alternatives, nor does it mention prerequisites such as obtaining the current deployment ID via github_get_deployments. No exclusions or 'when not to use' are stated.

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

Deploy Server