jenkins-http-mcp-server

jenkins_get_build_artifacts

Read-only

Retrieve artifacts generated by a Jenkins build from its JSON API response. Specify the job and build number to get a list of exported artifact files.

Instructions

List artifacts exported on a build JSON API response.

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

First observedv0.1.0May 6, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds modest context by indicating the artifacts are read from the build JSON API response rather than downloaded directly. However, it does not clarify what 'exported' means or confirm that no artifact download is started.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with the core action front-loaded. It has no filler, but the phrasing 'exported on a build JSON API response' is slightly awkward and could be more direct.

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?

Given the tool's simplicity, output schema presence, and read-only annotations, the description is adequate for basic identification. However, it lacks parameter guidance and explicit differentiation from artifact-download siblings, so an agent may not have enough context to invoke it correctly in ambiguous situations.

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 missing parameter documentation. It does not explain what 'job' and 'build' mean, how the array form of 'job' behaves, or why 'build' can be an integer or string. The parameter names are somewhat self-explanatory, but the description adds no semantic detail.

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 clearly identifies the action ('List artifacts') and the resource ('a build JSON API response'). It is distinct from download-related siblings like jenkins_start_artifact_download because it frames the tool as reading a list, though the phrase 'exported on' is somewhat awkward and could be clearer.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as jenkins_get_build or jenkins_start_artifact_download. The description implies a listing use case, but it does not explicitly state when this tool is preferred or when another tool should be used instead.

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

Deploy Server