jenkins-http-mcp-server

jenkins_start_workspace_path_download

Destructive

Start or join a guarded capture of workspace files/folders from a Jenkins job and retrieve the exact console log.

Instructions

Start or join a guarded workspace file/folder capture plus exact console log.

Input Schema

TableJSON Schema

Name	Required	Default
`job`	Yes
`kind`	Yes
`build`	No	lastBuild
`force_refresh`	No
`workspace_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_workspace_path_downloadDictOutput"New value: +"ToolSuccess"

Addedv1.0.0Sep 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds some useful context by saying the operation is 'guarded' and can be started or joined, which hints at concurrency and statefulness. However, it does not explain what destructive side effects occur or how a caller should manage the resulting operation.

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 compact sentence with no filler. It loses a point because 'guarded' and 'plus exact console log' are vague enough that brevity comes at the expense of clarity.

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?

There is an output schema, so return shape is covered, but for a stateful, destructive operation with five parameters and zero schema descriptions, the description is far too thin. It lacks parameter semantics, lifecycle guidance, and any relationship to the status/cancel/cleanup siblings, leaving the agent to guess at correct invocation.

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?

The schema has 0% description coverage, and the description compensates very little. It hints at 'workspace_path' and possibly 'kind' via 'file/folder', but job, build, and force_refresh are entirely unexplained, and no values or defaults for 'kind' are given.

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 operation ('start or join') on a specific resource ('workspace file/folder capture') and adds that an exact console log is included. It is distinguishable from the bundled workspace download siblings, though 'guarded' and 'exact console log' remain somewhat ambiguous.

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?

There is no guidance about when to use this tool instead of jenkins_start_workspace_bundle_download, jenkins_get_workspace_bundle_status, or related cancel/cleanup tools. The phrase 'start or join' implies an asynchronous or resumable workflow, but no explicit context, prerequisites, or alternative conditions are provided.

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

Deploy Server