jenkins-http-mcp-server

jenkins_get_queue_item

Read-only

Retrieve a specific Jenkins build queue item by its ID to inspect its status and details.

Instructions

Get one Jenkins queue item by ID.

Input Schema

TableJSON Schema

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

First observedv0.1.0May 6, 2026

TDQS

A3.9/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, so the safety profile is covered. The description's read-only 'Get' aligns with the annotations and adds no contradictory behavior, though it does not disclose additional contextual details like error behavior.

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?

One sentence with no filler, core information front-loaded, and every word contributes to the meaning. It is appropriately sized for the simplicity of the operation.

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?

For a simple read-only fetch by ID, the description is mostly complete: the output schema covers return values and annotations cover the safety profile. It could add a brief pointer to jenkins_list_queue for discovering IDs, but this is an enhancement rather than a critical 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?

Schema description coverage is 0%, so the description had the burden of explaining item_id. It only restates 'by ID', adding little beyond the schema's property name and integer type. It does not explain where the queue item ID comes from or how it relates to jenkins_list_queue.

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 ('Get'), names the exact resource ('Jenkins queue item'), and specifies the scope ('by ID'). This clearly differentiates it from sibling tools like jenkins_list_queue, which lists multiple items, and jenkins_cancel_queue_item, which mutates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'by ID' qualifier gives clear context: use this tool when you need one specific queue item and already have its ID. It does not explicitly mention alternatives or exclusions, but the intended usage is unambiguous.

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

Deploy Server