Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

List Artifacts

list_artifacts

Read-onlyIdempotent

List archived artifacts for a Jenkins build, optionally including file sizes and the download base URL. Use it to inspect build outputs before reading text artifacts or downloading binaries.

Instructions

Archived artifacts of a build (relative paths, optionally with sizes) and the download base URL. Read text artifacts with read_artifact; binaries (jar, zip, pdf, xlsx...) are never sent to the model - use the download URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job": "<job>"
    },
    "name": "list_artifacts"
  }
}

Input Schema

Name	Required	Description
`job`	Yes	Job full name like 'cd/master/my-app' (folders separated by '/'), or a Jenkins job/build URL (instance is then detected from the URL).
`build`	No	Build number or permalink: lastBuild, lastFailedBuild, lastSuccessfulBuild, lastCompletedBuild, lastUnsuccessfulBuild. Empty = build from the URL, else lastBuild.
`limit`	No
`sizes`	No	Also show file sizes (one HEAD request per file, first 50)
`instance`	No	Jenkins instance name from list_instances. Empty = default instance.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: binary payloads are never sent to the model and the tool surfaces a download base URL instead. It does not mention output volume or pagination behavior, which keeps it short of a 5.

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?

Two tight sentences with zero filler; the return content is front-loaded and the follow-up action (read vs. download) comes second. Every clause carries information.

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?

An output schema exists, so return shape needn't be explained, and the description covers the one non-obvious constraint (binaries excluded). The remaining gap is the unexplained `limit` cap on listing, which the agent would have to infer from the schema default alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80% and the schema documents job, build, sizes, and instance thoroughly. The description only reinforces the optional sizes behavior already described in the schema, and it says nothing about the undocumented `limit` parameter. Baseline 3 is appropriate.

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?

States exactly what is returned: archived artifact relative paths, optional sizes, and the download base URL for a given build. It also draws the line against read_artifact and the binary-download path, so an agent can distinguish it from siblings like compare_artifacts, list_workspace, and read_artifact without opening schemas.

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

Usage Guidelines5/5

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

Explicitly routes the agent: text artifacts go to read_artifact, binaries (jar, zip, pdf, xlsx) must go through the download URL. This names the alternative and the condition that selects it, which is exactly the when/when-not guidance needed.

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