jenkins-http-mcp-server

jenkins_list_plugins

Read-only

List installed Jenkins plugins with details like version, status, and update availability using the pluginManager API.

Instructions

List installed Jenkins plugins visible through pluginManager/api/json.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tree`	No		plugins[shortName,longName,version,active,enabled,pinned,hasUpdate,deleted]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.0.0Sep 6, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Structured content returned by successful Jenkins tools."

addedOutput schema / properties

Added value: +{
+  "data": {
+    "title": "Data"
+  },
+  "ok": {
+    "const": true,
+    "title": "Ok",
+    "type": "boolean"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "ok",
+  "data"
+]
```

changedOutput schema / title

Previous value: -"jenkins_list_pluginsDictOutput"New value: +"ToolSuccess"

First observedv0.1.0May 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint and openWorldHint annotations already convey that this is a safe, non-mutating query. The description adds the source endpoint and the 'visible' qualifier, which hints at filtering, but it does not clarify behavior such as whether disabled or hidden plugins are included or how pagination works. Still, it does not contradict annotations and adds some context.

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?

The description is a single, compact sentence that conveys the essential purpose without filler. It is front-loaded with the action and resource, making it easy for an agent to scan.

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?

The presence of an output schema and read-only annotations lightens the load, but the near-total lack of parameter guidance and usage context leaves the definition slightly under-specified. The agent can still invoke it correctly using the default, but the description alone would not fully support parameter customization.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter, tree, with 0% description coverage. The description does not mention or explain the tree parameter at all, leaving the agent to infer its meaning from the default value alone. This is a notable gap for a parameter that controls response field selection.

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?

The description states a specific action (List) and resource (installed Jenkins plugins), and adds the scoping detail 'visible through pluginManager/api/json'. This is unambiguous and clearly distinct from all sibling tools, none of which list plugins.

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?

No guidance is provided about when to use this tool versus alternatives. While no sibling directly overlaps, the description does not mention related tools such as jenkins_get_json or jenkins_list_jobs, nor any conditions that would make this the preferred choice.

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

Deploy Server