MCP Jenkins

Get All Plugins

get_all_plugins

Retrieve all installed plugins from a Jenkins instance, with configurable depth to include dependencies.

Instructions

Get all installed plugins from Jenkins

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_plugins"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	The depth of the information to retrieve. Default is 2 (includes dependencies).

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

B3.2/5.0

Behavior3/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. It implies a read-only listing operation and 'installed' narrows scope versus available plugins, but it says nothing about permissions required, result size, pagination, or cost of the call.

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?

A single front-loaded sentence with no wasted words. It is efficient, though minimal enough that it could have afforded one more clause of guidance without bloat.

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 return values need not be explained, and the sole parameter is well documented. What remains missing is any read-only/permission context (no annotations) and sibling differentiation, which matters given the crowded plugin-related tool family.

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% and the single 'depth' parameter is fully documented in the schema, including its default and the meaning of depth 2. The description adds no further meaning about depth, so the baseline of 3 applies.

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 all installed plugins from Jenkins'), which is clear on its own terms. However, it does not distinguish itself from near-identical siblings such as get_plugin, get_plugins_with_updates, get_plugins_with_problems, or get_plugin_dependency_graph, leaving the agent to infer the difference from the name alone.

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 explicit guidance on when to choose this tool over get_plugin (single plugin) or the filtered variants like get_plugins_with_updates. The word 'all' hints at a full listing, but no alternatives or exclusions are named.

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