jenkins-http-mcp-server

jenkins_create_job

Create a top-level Jenkins job from config.xml, requiring write and job-config flags to complete.

Instructions

Create a top-level job from config.xml. Requires write and job-config flags.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`config_xml`	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_create_jobDictOutput"New value: +"ToolSuccess"

First observedv0.1.0May 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already communicate readOnly=false, idempotent=false, destructive=false, and openWorld=true. The description adds useful behavioral detail by stating that write and job-config permissions are required and that the tool only creates top-level jobs, not folder-scoped jobs. 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.

Conciseness5/5

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

Two short sentences with the primary action front-loaded. The permission requirement is the only extra information, and there is no redundancy with the schema or annotations.

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?

For a simple two-parameter creation tool with an output schema and annotations, the description is broadly sufficient. However, it omits likely failure conditions such as duplicate job names or invalid config XML, and it gives no guidance about when to prefer sibling tools for related operations.

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 0%, so the description must compensate. It loosely explains that config_xml contains the job's config.xml, and 'name' is self-explanatory, but it does not clarify format, uniqueness constraints, or expected XML structure. This is minimally adequate.

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 ('Create') and names the resource ('top-level job') plus the source artifact ('config.xml'). This clearly distinguishes it from sibling tools like jenkins_update_job_config, jenkins_copy_job, and jenkins_delete_job.

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 this tool is for creating a new top-level Jenkins job from XML, and adds a permission prerequisite. However, it does not explicitly state when not to use it or name alternatives such as updating an existing job or copying a job.

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

Deploy Server