MCP Jenkins

List Builds

list_builds

Retrieve recent builds for a Jenkins job, newest first, with an optional limit to control results.

Instructions

List the most recent builds of a job in Jenkins, newest first

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": "list_builds"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many builds to return, 1-100 (default 20)
`fullname`	Yes	The fullname of the job

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses ordering ('newest first') and that results are scoped to a job, and 'List' implies read-only behavior, but it does not state permissions, pagination semantics, or other operational details.

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 front-loaded sentence with no unnecessary wording. Every phrase contributes to scope, resource, or ordering.

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 two-parameter read tool with an output schema and full parameter descriptions, the description covers the core operation. It remains incomplete because it does not explicitly route the agent away from sibling tools or describe behavioral constraints beyond ordering.

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 the input schema already documents both parameters. The description adds only indirect context via 'job' and 'most recent' and does not add constraints or format details beyond the schema.

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 a specific verb (List), resource (builds), scope (of a job in Jenkins), and ordering (newest first). It implicitly distinguishes itself from get_build (single build) and get_running_builds (running builds), even though it does not name those siblings.

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 'most recent builds of a job': use this to retrieve recent historical builds. However, there is no explicit when-to-use or when-not-to-use guidance, and it does not mention alternatives such as get_build or get_running_builds.

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