jenkins-http-mcp-server

jenkins_stop_build

Destructive

Stop a running Jenkins build by providing the job and build number. Requires write access enabled (JENKINS_MCP_ENABLE_WRITES=1).

Instructions

Stop a running build. Requires JENKINS_MCP_ENABLE_WRITES=1.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job`	Yes
`build`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.0.0Sep 6, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Structured content returned by successful Jenkins tools."

addedOutput schema / properties

Added value: +{
+  "data": {
+    "title": "Data"
+  },
+  "ok": {
+    "const": true,
+    "title": "Ok",
+    "type": "boolean"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "ok",
+  "data"
+]
```

changedOutput schema / title

Previous value: -"jenkins_stop_buildDictOutput"New value: +"ToolSuccess"

First observedv0.1.0May 6, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not contradicting them. It adds the critical prerequisite, JENKINS_MCP_ENABLE_WRITES=1, which is beyond the structured annotations and is essential for the agent to know before invoking the tool. It does not disclose consequences for already-finished builds, but the added context is valuable.

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 exactly two sentences with no fluff. The main action is front-loaded, and the prerequisite follows immediately. Every word earns its place.

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?

The description mentions a critical environment variable and the action, but it lacks parameter semantics and usage guidance. Given this is a destructive write operation with 0% parameter schema coverage, an agent would still be uncertain how to correctly populate the 'job' and 'build' arguments, especially with their polymorphic types. The output schema exists but does not compensate for these gaps.

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?

Schema description coverage is 0% and the description does not explain either parameter. The schema shows 'job' accepts string or array and 'build' accepts integer or string, but the agent receives no guidance on what values are expected, what the array means, or the relationship between the two parameters. The description entirely fails to compensate for the missing schema descriptions.

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 uses a specific verb ('Stop') with a clear resource ('a running build'), which unambiguously identifies the tool's function. It also naturally differentiates from sibling tools like jenkins_cancel_queue_item (which cancels queued items) and jenkins_delete_job (which deletes jobs).

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 states only a prerequisite (JENKINS_MCP_ENABLE_WRITES=1) and provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, how it relates to jenkins_cancel_queue_item, or what conditions justify stopping a build.

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

Deploy Server