jenkins-http-mcp-server

jenkins_list_builds

Read-only

Retrieve recent build details for a Jenkins job, including number, URL, result, and timestamp. Specify a single job or multiple jobs to monitor build history.

Instructions

List recent builds for a job.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job`	Yes
`tree`	No		builds[number,url,result,building,timestamp,duration]

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

First observedv0.1.0May 6, 2026

TDQS

A3.7/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 description needs to add context beyond those. It adds 'recent' to clarify scope but does not disclose details like build ordering, pagination limits, or how the tree parameter changes the response. This is adequate for a simple read-only list but not rich.

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 sentence with no filler words. It states the action and target resource directly, making it highly scannable and efficient for an agent.

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 list operation with an output schema provided, so return values are already covered. The description plus annotations are nearly sufficient for successful invocation. The main gap is the lack of tree parameter guidance, but the default value and simple invocation path make the tool usable without it.

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 must compensate for undocumented parameters. It only clarifies the 'job' parameter by mentioning 'for a job.' The 'tree' parameter is left unexplained beyond its default string, which is not self-evident. The description does not sufficiently bridge the schema coverage gap.

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 clearly states a specific verb and resource: 'List recent builds for a job.' This unambiguously identifies the tool's function and differentiates it from siblings like jenkins_get_build or jenkins_get_build_log, which target individual builds or logs rather than listing recent builds.

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 intended use case is implied: when you need a listing of recent builds for a specific job. However, there is no explicit guidance about when to prefer this over sibling tools or any exclusions, such as when to use jenkins_get_build instead. The usage context is inferable but not directly stated.

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

Deploy Server