Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

Diff Job Config

diff_job_config

Read-onlyIdempotent

Compare two Jenkins job configuration versions to reveal semantic changes and a unified XML diff with secrets masked; defaults to newest versus previous.

Instructions

What changed between two configuration versions of a job: a semantic list ('triggers: cron: H 3 * * * -> cron: H 2 * * *', parameters, SCM, script path, retention...) plus a unified diff of the XML. Secrets are masked in both. Default: the newest version against the one before it.

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": {
      "job": "<job>"
    },
    "name": "diff_job_config"
  }
}

Input Schema

Name	Required	Description
`job`	Yes	Job full name like 'cd/master/my-app' (folders separated by '/'), or a Jenkins job/build URL (instance is then detected from the URL).
`newer`	No	Timestamp, or 'current' for the live config.xml; empty = the newest version
`older`	No	Timestamp from get_job_config_history; empty = the version before `newer`
`instance`	No	Jenkins instance name from list_instances. Empty = default instance.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds real value with the secrets-masking guarantee and the output shape (semantic change list + unified XML diff). It does not discuss large-diff handling or failure modes when a version is missing, which keeps it from a 5.

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?

Two tight sentences: output content first, masking and default behavior second. No filler, and the most decision-relevant facts are front-loaded.

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?

With an output schema present and full parameter coverage, the description needn't detail return values, and it correctly covers masking and default selection. A note on behavior when history is empty or a version is not found would make it complete.

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 baseline is 3. The description restates the default comparison (newest vs previous) that the schema's `newer`/`older` defaults already encode, adding little 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 (diff) and resource (job configuration versions) and enumerates what the diff contains (triggers, parameters, SCM, script path, retention, plus unified XML diff). An agent can distinguish it from get_job_config and get_job_config_history directly from the text.

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?

Explains the default comparison behavior (newest vs the one before) and implicitly routes to get_job_config_history by naming it as the source of the `older` timestamp. Missing an explicit 'use this instead of X' statement for the single-config siblings, but usage context is clear.

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