jenkins-http-mcp-server

jenkins_cancel_artifact_download

Destructive

Cancel an ongoing artifact download from Jenkins by providing its operation ID, stopping the transfer to save time and bandwidth.

Instructions

Request cancellation of a running artifact download.

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

Addedv1.0.0Sep 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already indicate this is destructive and non-idempotent. The description adds the useful nuance that this is a cancellation 'request' rather than a guaranteed immediate cancel, and that it applies only to 'running' downloads. It does not elaborate on side effects or state changes, but the annotations cover the core safety profile.

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. It conveys the action, resource, and state condition efficiently.

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 simple one-parameter shape and existing output schema, the description is mostly adequate, but it leaves the source of operation_id implicit and gives no guidance on cancellation semantics beyond 'request.' This is sufficient for a minimal viable definition but not fully complete.

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 0% schema description coverage and the description does not explain where the ID comes from or how it is obtained. An agent must infer from sibling tools that the operation_id refers to a previously started artifact download, which is not explicitly stated.

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 states a specific verb ('Request cancellation') and a clear resource ('running artifact download'). It also distinguishes itself from sibling tools like cancel_workspace_bundle_download and get_artifact_download_status by naming the exact operation it targets.

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 word 'running' gives implied usage context: this tool is for canceling an artifact download that is currently in progress. However, it does not explicitly mention when not to use it, nor does it name alternatives such as cancel_workspace_bundle_download for workspace bundle downloads.

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

Deploy Server