jenkins-http-mcp-server

jenkins_disable_job

Destructive

Disable a Jenkins job to prevent it from running. Requires write access enabled on the server.

Instructions

Disable a job. Requires JENKINS_MCP_ENABLE_WRITES=1.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job`	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_disable_jobDictOutput"New value: +"ToolSuccess"

First observedv0.1.0May 6, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare the write and destructive nature, so the bar is lower. The description adds one useful operational context beyond annotations: the JENKINS_MCP_ENABLE_WRITES=1 requirement. It does not disclose downstream effects on queued/running builds or that the operation is reversible via enable_job. No contradiction with annotations.

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

Conciseness4/5

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

Two short sentences, front-loaded with the verb, zero filler. Both sentences earn their place, though the size is minimal rather than richly informative.

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

Completeness3/5

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

Complexity is low (single required parameter) and an output schema exists, so return values need no explanation. The env var gate is covered and annotations carry the safety profile, but the missing consequences (effect on running builds, reversibility) leave the picture slightly incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it adds nothing beyond the word "job" already present in the schema. It does not explain that the parameter accepts an array to disable multiple jobs, nor any naming format expectations.

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?

"Disable a job" uses a specific verb and resource, making the action unambiguous. It is clearly distinct from sibling actions like enable, delete, or update, though it does not explicitly name the alternatives.

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 an environmental prerequisite (JENKINS_MCP_ENABLE_WRITES=1) but gives no guidance on when to choose disable over enable_job, delete_job, or update_job_config, nor any exclusion conditions. This is a gate, not usage direction.

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

Deploy Server