jenkins-http-mcp-server

jenkins_cleanup_workspace_bundle_operations

Destructive

Delete completed Jenkins workspace operations older than the requested age, optionally capping the number of operations removed to manage cleanup efficiently.

Instructions

Delete bounded, terminal local workspace operations older than the requested age.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`max_operations`	No
`older_than_days`	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_cleanup_workspace_bundle_operationsDictOutput"New value: +"ToolSuccess"

Addedv1.0.0Sep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description aligns with destructiveHint=true and adds valuable scoping: only bounded, terminal, local, and older-than-age items are deleted. It does not, however, clarify whether deletion is permanent or whether it removes local bundle artifacts vs. operation records, so the behavioral picture is only partially complete.

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 tightly written sentence with the action verb at the beginning, no filler, and every qualifier ('bounded', 'terminal', 'local', 'older than') contributing meaning. This is appropriately concise.

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?

For a simple two-parameter destructive tool with an output schema, the description is nearly sufficient, but it leaves the meaning of 'terminal local workspace operations' implicit. An agent without prior Jenkins bundle-domain knowledge would still have to infer what resource is actually being deleted and when a local operation counts as terminal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. 'older than the requested age' clearly maps to older_than_days and 'bounded' hints at max_operations, but the description does not explain the bound's behavior or units. The schema's property titles and default values help close the gap.

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 uses a specific verb ('Delete') plus a scoped resource ('bounded, terminal local workspace operations') and a condition ('older than the requested age'). This makes the tool distinguishable from the sibling workspace bundle download/cancel/status tools. It would be a 5 if it unpacked the domain jargon ('terminal', 'workspace operations') slightly more.

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 phrase 'terminal' and 'older than the requested age' imply eligibility conditions, so an agent can infer when deletion is appropriate. However, the description never explicitly says to use this instead of cancel_workspace_bundle_download or get_workspace_bundle_status, nor does it state what to check before running a destructive cleanup.

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

Deploy Server