Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

Find Known Issues

find_known_issues

Read-onlyIdempotent

Matches a Jenkins build log or pasted error text against your team knowledge base, returning known issues with the first matching log line and documented fix.

Instructions

Look up the team knowledge base. With job (+build) the build log is matched against every entry in scope (instance/job); with text, a pasted error message is matched. Returns matching entries with the first matching log line and the documented fix. get_build_summary already does this automatically - use this tool for a pasted error or before writing a new entry.

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

Input Schema

Name	Required	Description
`job`	No	Job full name or Jenkins URL. Empty = not tied to a build.
`text`	No	Error text to look up instead of a build
`build`	No	Build number or permalink: lastBuild, lastFailedBuild, lastSuccessfulBuild, lastCompletedBuild, lastUnsuccessfulBuild. Empty = build from the URL, else lastBuild.
`instance`	No	Jenkins instance name from list_instances. Empty = default instance.
`include_drafts`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With readOnlyHint/idempotentHint already declaring a safe read, the description adds real behavior: matching happens against 'every entry in scope (instance/job)' and returns the first matching log line plus the documented fix. It does not mention how include_drafts changes results or any pagination/result-limit behavior, which is the main remaining gap.

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?

Four sentences, zero filler, front-loaded with the purpose before the mode split and the sibling routing note. Every sentence carries information the agent needs to call it correctly.

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 the description's extra note about return contents is bonus rather than required. Matching modes, scoping, and routing are all covered; only the include_drafts flag and any result-size limits are left unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the bar is already low, but the description still adds value by explaining the interaction of job+build versus text as alternate matching modes. The one fully undocumented parameter (include_drafts) gets no explanation in either schema or description.

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 and resource ('Look up the team knowledge base') and then spells out the two distinct matching modes: build-log matching with job (+build), and error-text matching with text. An agent can distinguish it from list_known_issues, get_known_issue, and get_build_summary without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names when to use it ('for a pasted error or before writing a new entry') and explicitly names the overlapping sibling ('get_build_summary already does this automatically'), so the agent knows this tool is for the non-automatic cases. When-to-use and alternative routing are both present.

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