Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

Failures Overview

failures_overview

Read-onlyIdempotent

Lists Jenkins jobs whose last build failed or is unstable within a chosen time window across one or all instances, so you can spot red jobs quickly.

Instructions

Jobs whose LAST build failed (and optionally is unstable) within the last hours, across one or all instances in parallel. Good for a morning check or 'what is red right now'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "failures_overview"
  }
}

Input Schema

Name	Required	Description	Default
`hours`	No
`folder`	No
`instance`	No	Instance name or 'all'	all
`include_unstable`	No
`limit_per_instance`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context about last-build semantics, optional unstable inclusion, and parallel querying across instances, but it does not explain limits, pagination, or result shape.

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 two compact sentences with no wasted language. The core filtering behavior is front-loaded before the usage example.

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 described. However, with five parameters and only 20% schema description coverage, the description is not complete enough to fully explain `folder` and `limit_per_instance` behavior for an overview tool.

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 low at 20%, so the description should compensate more. It clarifies `hours`, `include_unstable`, and `instance` ("one or all instances"), but it omits meaning for `folder` and `limit_per_instance`, leaving two of five parameters undocumented beyond type and default.

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 resource and filter: jobs whose LAST build failed within the last `hours`, optionally including unstable jobs, across one or all instances. This is clear and actionable, though it does not explicitly distinguish the tool from siblings such as recent_builds or list_jobs.

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

Usage Guidelines4/5

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

It gives clear usage context with "Good for a morning check or 'what is red right now'," which tells the agent when this overview is appropriate. It does not explicitly state when not to use it or name alternative tools for narrower queries.

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