MCP Jenkins

Get Pending Inputs

get_pending_inputs

List a Jenkins build's pending input steps, including input IDs and parameter definitions, so you can locate paused pipelines and respond to required input.

Instructions

Get the pending input steps of a specific build in Jenkins

A pipeline showing "Paused for Input" is waiting on an input step. This lists the input id and the parameter definitions the pipeline is waiting for.

Only the given build is inspected. With number=None that is the job's last build, so a paused build that is no longer the most recent one is not found that way — locate it with get_running_builds and pass its number explicitly.

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

Input Schema

Name	Required	Description	Default
`number`	No	The number of the build, if None, check the last build
`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

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the burden and discloses the key behavioral traits: only the given build is inspected, and the None default silently targets the job's last build rather than searching. The read-only nature is only implied by "Get"/"lists" rather than stated, which keeps it short of 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?

Three short blocks: purpose first, then the domain cue and return shape, then the scoping caveat. No filler, and the most failure-prone detail (the None default) is surfaced in its own paragraph rather than buried.

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

Completeness5/5

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

For a two-parameter read tool with a full output schema and complete schema coverage, nothing an agent needs in order to call it correctly is missing: the target, the returned content, and the lookup pitfall are all covered.

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 100%, so baseline is 3, but the description adds real meaning beyond the schema's "if None, check the last build" note by spelling out the consequence that a non-latest paused build will not be found that way and how to work around it. That is genuine semantic value for the number parameter.

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 ("Get the pending input steps of a specific build in Jenkins") and then defines the domain signal ("Paused for Input") that identifies the target state. It also says what is returned at a conceptual level (input id plus parameter definitions), which is enough to distinguish it from get_build_parameters and get_build.

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?

Gives an explicit trigger (a pipeline paused for input) and an explicit failure mode with the alternative: when number=None the last build is checked, so a paused build that is no longer latest must be located via get_running_builds and passed explicitly. That is when-to-use, when-not-to-use, and the sibling to use instead.

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