MCP Jenkins

Get Item

get_item

Retrieve a specific Jenkins item by its full name to inspect jobs, views, or folders. Use it to access item details for review and build operations.

Instructions

Get specific item from Jenkins

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

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

C2.4/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 behavioral burden. 'Get' implies a read operation, but the description does not state permission requirements, error behavior, or whether the operation is safe/non-destructive, and it provides little context beyond the verb.

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?

The definition is a single short, front-loaded sentence with no wasted clauses. It is structurally clean, though it is arguably over-terse for the amount of context an agent needs.

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

Completeness2/5

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

Although this is a simple one-parameter tool and an output schema exists, the description does not clarify what kind of item is meant or how it relates to the many sibling item tools. That leaves important selection context missing.

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?

The only parameter, fullname, has 100% schema description coverage. The description adds no format or semantic detail beyond saying it retrieves a specific item, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

The description essentially restates the tool name and title ('Get Item' / get_item) and adds only 'from Jenkins'. It does not specify what an 'item' is or how this differs from sibling tools such as get_item_config, get_item_summary, get_item_parameters, query_items, or get_all_items.

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 or when-not-to-use guidance, and no alternatives are named. With many item-related sibling tools, an agent must infer the selection criteria without help.

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