jenkins-http-mcp-server

jenkins_list_queue

Read-only

List Jenkins queue items to monitor pending and blocked builds, including reasons, blocked status, and buildability.

Instructions

List visible Jenkins queue items.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tree`	No		items[id,url,why,blocked,buildable,stuck]

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

First observedv0.1.0May 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the 'visible' qualifier, which is useful, but does not mention behavior such as pagination, ordering, or the meaning of the default tree fields.

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 five-word sentence that front-loads the action and resource with no filler. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only listing tool with an output schema, read-only annotations, and an optional parameter carrying a sensible default. The description is adequate for basic invocation, although the undocumented tree parameter is a minor gap.

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?

There is one parameter, tree, with 0% schema description coverage, and the tool description does not explain it. The schema provides only a type and default value, which is insufficient for an agent to understand how the tree parameter controls the response fields.

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 states a specific verb ('List') and resource ('Jenkins queue items'), with 'visible' adding scope. It clearly distinguishes the listing operation from item-level tools like jenkins_get_queue_item and jenkins_cancel_queue_item, though it does not name them explicitly.

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 verb 'List' implies this tool is for enumerating queue items rather than inspecting a single item, so usage context is inferable. However, there is no explicit guidance about when to prefer this over jenkins_get_queue_item or how 'visible' should be interpreted.

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

Deploy Server