jenkins-http-mcp-server

jenkins_get_workspace_bundle_status

Destructive

Check the progress and final status of a Jenkins workspace bundle operation, including download/extract logs, bytes, speed, and paths. Use the operation ID to retrieve detailed updates.

Instructions

Get download/extract/log progress, bytes, speed, paths, and final status.

Input Schema

TableJSON Schema

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

Addedv1.0.0Sep 5, 2026

TDQS

B3.1/5.0

Behavior1/5

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

The description presents this as a read-only status retrieval ('Get ... progress ... and final status'), but the annotations declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. This is a direct contradiction between the described behavior and the annotation metadata, leaving the agent with conflicting safety expectations.

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?

The description is a single, compact sentence that front-loads the action and resource, then lists the relevant status dimensions. Every phrase earns its place with no filler or repetition.

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 a simple one-parameter status tool, the description lists output fields well, but it leaves out essential operational context: where operation_id comes from, how this tool relates to start/cancel/cleanup bundle operations, and whether repeated polling is expected. The contradictory destructiveHint annotation further undermines completeness.

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 only parameter, operation_id, has no schema description and 0% schema coverage. The tool description never explains what this ID represents, how to obtain it, or that it likely comes from a prior start_workspace_bundle_download call. The description focuses on output fields rather than parameter meaning.

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 and resource ('Get ... workspace bundle status') and enumerates the exact status fields returned: download/extract/log progress, bytes, speed, paths, and final status. This clearly distinguishes it from sibling tools like start_workspace_bundle_download and cancel_workspace_bundle_download.

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 that this is the polling/status tool for a workspace bundle download operation, but it never explicitly states when to use it (e.g., after starting a bundle download) or why it should be chosen over sibling tools like jenkins_get_artifact_download_status. Usage is inferable but not stated.

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

Deploy Server