jenkins-http-mcp-server

jenkins_get_build_log

Read-only

Fetch a Jenkins build's console log to inspect execution details, truncating output when it exceeds the configured byte limit.

Instructions

Get consoleText for a build, truncated by JENKINS_MCP_MAX_LOG_BYTES.

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

First observedv0.1.0May 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With readOnlyHint=true already declared, the description adds meaningful behavior by disclosing that the output is truncated by JENKINS_MCP_MAX_LOG_BYTES. This goes beyond the annotations and sets an expectation about log size, though it does not explain the limit's value or behavior for smaller logs.

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, and the key behavioral detail about truncation is included directly. It is concise while still conveying the core operation.

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?

For a simple read-only log fetch with an output schema present, the description covers the core operation and truncation behavior. However, it omits parameter semantics and any routing to chunked log retrieval, so an agent facing large logs or unusual job/build representations would be under-informed.

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%, and the description does not explain the job or build parameters. The names are recognizable, but the schema allows job as an array and build as integer or string, so an agent receives no guidance about valid forms or their meaning.

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: retrieving consoleText for a Jenkins build. The truncation note also distinguishes it from related log tools such as jenkins_get_build_log_chunk and jenkins_search_build_log.

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 truncation note implies this tool returns a bounded log snapshot, and the sibling list hints at chunked/search alternatives. However, the description never explicitly states when to prefer this tool over jenkins_get_build_log_chunk or how to retrieve an untruncated log, so usage context remains implicit.

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

Deploy Server