Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Job

get_job

Read-onlyIdempotent

Retrieve Jenkins job details, including type, health, build permalinks, recent builds, accepted parameters, and folder or multibranch children.

Instructions

Job details: type, health, permalinks (last/lastFailed/lastSuccessful build numbers), recent builds, parameters it accepts, and children if it is a folder/multibranch project.

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

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).
`instance`	No	Jenkins instance name from list_instances. Empty = default instance.
`recent_builds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful scope context (children are returned only for folder/multibranch jobs), but says nothing about permission requirements, instance resolution behavior, or whether the call is expensive on large jobs.

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?

A single front-loaded sentence with no filler, and every clause maps to something the tool actually returns. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so the description does not owe the agent return-value structure, and annotations cover the read-only profile. What is still missing is routing guidance against the many near-neighbors (get_job_config, get_build_summary, get_pipeline_info) and any explanation of the undocumented recent_builds count.

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 coverage is 67%: 'job' and 'instance' are well documented in the schema, while 'recent_builds' has no schema description at all. The description's phrase 'recent builds' gestures at that parameter but never states that it is a count, its default, or its upper bound, so the uncovered parameter stays underspecified.

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?

States a specific verb+resource (job details) and enumerates exactly what is returned: type, health, permalinks, recent builds, accepted parameters, and children for folder/multibranch jobs. That enumeration implicitly separates it from list_jobs (listing) and get_job_config (configuration), but no sibling is named explicitly.

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 rather than stated: an agent can infer 'call this to inspect one job' from the field list, and the children note hints at folder/multibranch traversal. There is no explicit when-to-use, when-not-to-use, or named alternative such as get_job_config or get_build_summary.

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