MCP Jenkins

Get Item Summary

get_item_summary

Summarizes a Jenkins job's configuration—repo, branch, steps, triggers, parameters, and downstream jobs—while redacting secret-like values and omitting credentials and long scripts for a quick overview.

Instructions

Summarise a job's configuration: repo and branch, steps, triggers, parameters, downstream jobs

A fraction of get_item_config. Secret-looking values are redacted, credential ids and long scripts are not reproduced. Use get_item_config only when you need the exact XML.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0+microtech.5Nov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that output is lossy (secret-looking values redacted, credential ids and long scripts not reproduced), which is exactly the kind of caveat an agent needs before relying on the result. It stops short of stating read-only/side-effect behavior outright, though 'Summarise' strongly implies a read.

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?

Content is front-loaded into the first sentence with the alternative and the redaction caveat following. Minor structural issue: the sentence splits awkwardly around 'downstream jobs / A fraction of get_item_config', making the relationship between the two tools slightly harder to parse than necessary.

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?

For a single-parameter summary tool with an output schema (so return shape needn't be explained), the description covers content, lossiness, and the alternative route. Only the interpretation of 'fullname' and the read-only nature are left implicit, which are small gaps given the schema coverage.

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% for the single parameter, so the schema already documents 'fullname'. The description adds no format, path syntax, or example for that value, so baseline 3 is appropriate 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (summarise) and resource (a job's configuration) and enumerates exactly what the summary contains: repo/branch, steps, triggers, parameters, downstream jobs. It also explicitly positions itself against get_item_config, so an agent can distinguish the two without opening either 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?

Gives an explicit selection rule: use this tool as a fraction of get_item_config, and use get_item_config 'only when you need the exact XML.' That is a clear when-to-use / when-to-use-the-alternative pair, not just an implied preference.

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