jenkins-http-mcp-server

jenkins_start_artifact_download

Initiate a gated asynchronous download of a specific archived build artifact from a Jenkins job to your local disk.

Instructions

Start a gated async download of one archived build artifact to local disk.

Input Schema

TableJSON Schema

Name	Required	Default
`job`	Yes
`build`	No	lastBuild
`artifact_path`	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_start_artifact_downloadDictOutput"New value: +"ToolSuccess"

Addedv1.0.0Sep 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already indicate non-readonly and non-idempotent behavior, and the description adds useful context by revealing that the download is asynchronous, gated, and writes to local disk. However, 'gated' is left unexplained, and there is no mention of whether a gate requires approval or what local path is used.

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?

A single, front-loaded sentence with no filler or redundancy. It immediately names the action, the object, and the execution mode, making the definition easy to scan.

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?

For an async initiation tool with no parameter descriptions, no explicit status-check guidance, and no explanation of 'gated', the one-line description leaves meaningful gaps. An agent may know to start the download but not how to construct valid arguments or how to monitor completion, even though an output schema exists.

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 for the lack of parameter documentation. It does not explain how 'job' (which may be a string or array), 'build' (which defaults to lastBuild), or 'artifact_path' should be specified. The only hint is the word 'artifact', which adds minimal value beyond the schema property names.

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 uses a specific verb ('Start') and clearly identifies the resource ('one archived build artifact') and destination ('local disk'). It also signals the async/gated nature, which helps distinguish it from status and cancellation siblings, though it does not explicitly name those alternatives.

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 phrase 'Start a gated async download' implies this is the initiation step of a multi-step download workflow, but it does not explicitly state when to use it versus the workspace download tools or when to follow up with status/cancel tools. Usage context is implied rather than directly explained.

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

Deploy Server