jenkins-http-mcp-server

jenkins_get_test_report

Read-only

Fetch test results for a specific Jenkins job and build, using the data provided by test-report plugins such as JUnit.

Instructions

Get /testReport/api/json when a test-report plugin such as JUnit provides it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job`	Yes
`build`	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_test_reportDictOutput"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 description does not need to re-establish safety. It adds useful context about the endpoint and plugin dependency, but does not disclose behavior when no test report is available or how failures are surfaced. This is acceptable but not richly transparent.

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, front-loaded sentence with no filler. It names the endpoint, the precondition, and an example plugin, earning its place with minimal word count.

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 tool with an output schema and readOnly/openWorld annotations, the description covers the essential context: what endpoint is accessed and when it is applicable. It could add a note about what happens when no test-report plugin exists, but overall the tool is simple enough that the description is largely 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?

Schema description coverage is 0%, so the description should compensate for the undocumented job and build parameters. It does not explain that job can be a string or array representing a folder path, nor whether build accepts a number, build name, or both. The parameter names are self-evident at a basic level, but meaningful type semantics are missing.

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 and resource: 'Get /testReport/api/json'. It also identifies the key precondition that a test-report plugin such as JUnit must provide the report, which clearly distinguishes this tool from generic Jenkins JSON or build retrieval tools.

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 description gives a clear usage context: use it when a test-report plugin provides /testReport/api/json. It does not name sibling alternatives or explicitly state when not to use it, but the conditional wording gives enough guidance for an agent to select it appropriately.

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

Deploy Server