Skip to main content
Glama
mdtahmidhossain

jenkins-http-mcp-server

by mdtahmidhossain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jenkins_cancel_workspace_bundle_download

Destructive

Cancel a running workspace bundle operation to stop an in-progress download or transfer. Use when you need to abort a bundle request.

Instructions

Request cancellation of a running workspace bundle operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • 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_cancel_workspace_bundle_downloadDictOutput"New value: +"ToolSuccess"
  2. Addedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true, so the cancellation is appropriately flagged as destructive. The description adds the useful context that the operation must be 'running', but it does not clarify whether cancellation is asynchronous, whether it can be undone, or what happens to the in-progress operation beyond that hint.

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, front-loaded sentence with no filler or repetition. It states the action and target clearly while staying very short, earning its place.

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?

Given the tool's low complexity—one required parameter and an output schema—the description is minimally adequate for selecting and invoking it. However, it omits usage guidance and does not clarify how operation_id connects to the broader workspace bundle lifecycle, leaving some burden on the agent to infer context from sibling tools.

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%, and the description does not compensate by explaining operation_id beyond naming the operation it refers to. The parameter name is self-descriptive and the tool context helps, but there is no detail on where the ID comes from or how to obtain it, so the description adds minimal value for parameter usage.

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 clearly states the action ('request cancellation') and the resource ('a running workspace bundle operation'), matching the tool name. It does not explicitly call out the sibling distinction from cancel_artifact_download, but the 'workspace bundle' phrasing provides enough specificity to separate it from artifact-download cancellation.

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 alternatives like cancel_artifact_download, get_workspace_bundle_status, or cleanup_workspace_bundle_operations. The phrase 'running workspace bundle operation' implies a precondition, but there is no explicit when-to-use or when-not-to-use guidance.

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

Deploy Server

Other Tools