MCP Jenkins

Get Build Console Output

get_build_console_output

Retrieve console output from a specific Jenkins build, or the last build, to inspect logs and diagnose failures. Filter by regex, skip lines with offset, and cap results with a line limit.

Instructions

Get the console output of a specific build in 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_console_output"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of lines to return after filtering and offset
`number`	No	The number of the build, if None, get the last build
`offset`	No	Number of lines to skip from the beginning after filtering, default 0
`pattern`	No	Optional regex pattern to filter lines (only matching lines are returned)
`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

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it adds nothing beyond the one-line purpose. It does not mention whether the console log requires build completion, whether output is truncated by default, whether access permissions apply, or whether the call is expensive for very long logs.

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?

A single short sentence with no filler, and the core purpose is front-loaded. It is efficient, though its brevity reflects under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool that supports regex filtering, offset, and line limiting, the description says nothing about result shape, truncation behavior, or how filtering interacts with pagination. The output schema covers return values, but the behavioral context around large console logs is missing entirely.

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%, and the schema already explains limit, offset, pattern, number, and fullname in detail, including the 'None means last build' semantics. The description adds no meaning beyond that, so the baseline of 3 applies.

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 names a specific verb and resource ('Get the console output') scoped to a 'specific build in Jenkins', so an agent immediately knows what it retrieves. It does not, however, distinguish itself from near siblings such as get_build, get_build_scripts, or get_build_test_report, which also return build-related data.

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 when-to-use guidance, no exclusions, and no named alternatives despite a crowded sibling set of build-inspection tools. The agent must infer on its own whether console output is preferable to get_build or get_build_scripts.

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