jenkins-http-mcp-server

jenkins_start_workspace_bundle_download

Destructive

Start or join a workspace bundle download for a Jenkins build, retrieving the full workspace capture and exact console log. Specify the job and build, or force a refresh to get a new bundle.

Instructions

Start or join a guarded workspace capture plus exact build console log.

Input Schema

TableJSON Schema

Name	Required	Default
`job`	Yes
`build`	No	lastBuild
`force_refresh`	No

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_workspace_bundle_downloadDictOutput"New value: +"ToolSuccess"

Addedv1.0.0Sep 5, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already indicate this is not read-only, not idempotent, and destructive. The description adds the notion of 'start or join' and 'guarded' capture, which hints at concurrent-access or reuse semantics beyond the annotations. However, it does not disclose what gets destroyed, whether bundles are overwritten, or what cleanup is required, so the added behavioral context is thin.

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?

The description is a single, front-loaded sentence with no filler. It is efficient and easy to parse. It sacrifices some clarity for brevity, leaving terms like 'guarded' undefined, but as a concise summary it works well.

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 having an output schema, this tool appears to be part of a multi-step bundle download workflow with sibling status/cancel/cleanup operations. The description does not explain where this tool fits in that workflow, what 'joining' means in practice, or how parameters affect the operation. Given 0% parameter coverage and no usage guidance, the description is not complete enough for an agent to call it confidently.

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 provides no parameter explanations. It does not clarify that 'job' is the Jenkins job to capture, that 'build' can be a numeric build or a string like 'lastBuild', or what 'force_refresh' actually forces. The schema only has titles and defaults, so the description must compensate but does not.

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 names a specific action ('Start or join') and a resource ('guarded workspace capture') plus an additional deliverable ('exact build console log'). This distinguishes it from simple log-fetching tools and indicates it starts a bundle download. However, 'guarded workspace capture' is somewhat jargon-heavy and not fully self-explanatory.

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?

No guidance is given about when to use this tool versus siblings like start_workspace_path_download, get_workspace_bundle_status, or cancel_workspace_bundle_download. The phrase 'start or join' hints at idempotent/join behavior but does not explain the workflow or exclusion conditions. An agent gets no help routing between the many bundle/workspace-related sibling tools.

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

Deploy Server