MCP Jenkins

Get Build Artifact

get_build_artifact

Download a specific Jenkins build artifact by job name, build number, and relative path; returns binaries as base64 and text files as plain text.

Instructions

Download an artifact from a specific build in Jenkins

Binary files are returned as base64-encoded content; text files are returned as plain text.

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": {
      "fullname": "<fullname>",
      "relative_path": "<relative_path>"
    },
    "name": "get_build_artifact"
  }
}

Input Schema

Name	Required	Description
`number`	No	The number of the build, if None, get the last build
`fullname`	Yes	The fullname of the job
`relative_path`	Yes	The relative path of the artifact (e.g. playwright-report/index.html)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0+microtech.5Nov 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations exist, so the description bears the full burden. It does add real behavioral value by disclosing the return encoding (base64 for binary, plain text for text), but it omits permission/auth requirements, artifact size limits, and confirmation that the operation is a non-destructive read.

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 short sentences with no waste: purpose first, then the non-obvious return-format detail. Every sentence earns its place and the key information is front-loaded.

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?

An output schema exists, so return values need not be explained, and the parameter schema is fully documented. However, for a download tool with no annotations, the description leaves gaps around prerequisites, error cases (missing path, expired build), and how to obtain the relative path.

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 description coverage is 100%, so all three parameters (number, fullname, relative_path) are already documented, including the None-defaults-to-last-build behavior and a relative_path example. The description adds nothing beyond the schema, which is the baseline expectation here.

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 states a specific verb and resource: 'Download an artifact from a specific build in Jenkins.' That cleanly separates it from siblings like get_build_console_output or get_build_test_report, but it never names its closest siblings (get_all_build_artifacts, get_build_artifact_url), so the agent must infer the distinction.

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?

There is no explicit when-to-use or when-not-to-use guidance. The agent is not told how to discover a valid relative_path (presumably via get_all_build_artifacts) or when this tool is preferable to get_build_artifact_url; usage is only implicit in the wording.

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