MCP Jenkins

Get Item Parameters

get_item_parameters

Retrieve parameter definitions for a Jenkins job using its full name to inspect required build inputs before triggering or configuring a run.

Instructions

Get the parameter definitions of a Jenkins job

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

Input Schema

Name	Required	Description	Default
`fullname`	Yes	The fullname of the item

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 provided, so the description carries the full disclosure burden and adds nothing beyond the read semantics implied by 'Get'. It does not state auth requirements, what happens when the fullname does not exist (empty list vs error), or whether disabled/plugin-provided parameters are included. The presence of an output schema offsets the need to describe return values, which keeps this above a 1.

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?

One front-loaded sentence with zero padding, which is efficient. It is arguably too terse for a tool with this many similar siblings, but no wording is wasted.

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 and the parameter is fully documented, so the mechanical calling requirements are covered. What is missing is the disambiguation an agent needs in a crowded namespace of item, job, and build parameter tools, which is precisely the gap the description should fill.

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 100% for the single required parameter, so the schema already documents fullname. The description's phrase 'of a Jenkins job' adds only marginal clarity by mapping the opaque 'item' in the schema to a job; baseline 3 applies when the schema does the heavy lifting.

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 and resource: get the parameter definitions of a Jenkins job. An agent can tell this returns job-level parameter definitions rather than build outputs. It does not, however, distinguish itself from close siblings such as get_item or get_build_parameters, which also return parameter-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 at all. With siblings named get_build_parameters, get_item, and get_item_config, an agent has to infer whether this returns the parameter schema of a job versus the parameter values attached to a build. The description offers no exclusions or alternative routing.

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