MCP Jenkins

Get Build Test Failures

get_build_test_failures

Retrieve failing tests and error details for a Jenkins build, including all matrix configurations, to diagnose build failures quickly.

Instructions

Get the failing tests of a specific build in Jenkins, with their error details

For a matrix build, the failures of all configurations are returned, each with the URL of its configuration build.

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>"
    },
    "name": "get_build_test_failures"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of failures to return, 1-200 (None means 200)
`number`	No	The number of the build, if None, get the last build
`fullname`	Yes	The fullname of the job
`max_stack_trace_length`	No	Stack traces longer than this are cut to this many characters

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

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does add real value: it discloses that error details are included and that matrix builds fan out to all configurations with per-configuration URLs. It omits that the call is read-only, how failures are capped/truncated (only in the schema), and any auth or permission expectations.

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, front-loaded with the core action and followed by the one non-obvious nuance (matrix builds). No filler or repetition of schema content.

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 structure need not be described, and every parameter is documented in the schema. The description covers the one surprising behavior (multi-configuration fan-out); it is only slightly thin regarding read-only semantics and failure limits given the absence of annotations.

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 four parameters (fullname, number, limit, max_stack_trace_length) are already documented in the schema; baseline 3 applies. The description adds no parameter-level meaning beyond what the schema states.

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?

States a specific verb and resource ('Get the failing tests of a specific build in Jenkins') plus the payload ('error details'), which clearly separates it from the broader get_build_test_report sibling. It never names that sibling explicitly, so the differentiation is implicit rather than stated.

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?

Usage is implied by the name and the phrase 'failing tests' (diagnose a broken build), but there is no explicit when-to-use, when-not-to-use, or pointer to get_build_test_report for the full report. The matrix-build sentence adds context about scope but is not selection guidance.

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