MCP Jenkins

Get Build

get_build

Fetch specific Jenkins build information using the full job name and optional build number, or retrieve the last build when no number is supplied.

Instructions

Get specific build info from Jenkins

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

Input Schema

Name	Required	Description	Default
`number`	No	The number of the build, if None, get the last build
`fullname`	Yes	The fullname of the job

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

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, but it only says "Get specific build info" and discloses nothing about read-only safety, return contents, error behavior, or permissions. The output schema helps with return shape, but the description itself adds almost no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. Its brevity is efficient, though it borders on under-specification given the many related tools.

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?

The tool has a simple two-parameter schema with full documentation and an output schema, so the core call mechanics are covered elsewhere. However, the description does not explain what kind of build information is returned or how this differs from specialized siblings, leaving a meaningful gap in a crowded tool namespace.

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%, with fullname and number already documented in the input schema, including the default behavior of returning the last build when number is null. The description adds no parameter meaning beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource ("Get specific build info from Jenkins"), so the basic purpose is understandable. However, "info" is vague and the description does not differentiate this tool from many siblings such as get_build_console_output, get_build_scripts, or get_build_test_report.

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 guidance on when to use this tool versus list_builds or the numerous get_build_* siblings. The agent must infer that this retrieves general build details rather than a specialized artifact like console output or test reports.

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