jenkins-http-mcp-server

jenkins_get_workspace_tree

Read-only

List the current workspace tree of a Jenkins job. Limit results by depth and entry count to inspect files without tying to a specific build.

Instructions

List a bounded live workspace tree. Paths are not bound to a build number.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job`	Yes
`max_depth`	No
`max_entries`	No
`workspace_path`	No

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_get_workspace_treeDictOutput"New value: +"ToolSuccess"

Addedv1.0.0Sep 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already communicate readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context: the listing is 'bounded' (matching max_depth/max_entries) and reflects the live workspace rather than a build-number-bound snapshot. No contradiction with annotations.

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?

Two short sentences with no wasted words. The first sentence front-loads the primary action, and the second earns its place by clarifying the live, non-build-bound nature of the paths.

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?

The output schema and readOnlyHint reduce the burden, but with four parameters and zero schema coverage, the definition leaves meaningful gaps: workspace_path interpretation, multi-job support implied by the array variant, and exactly what bounds apply. An agent can make a plausible guess, but the description is not fully complete for correct invocation in edge cases.

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?

Schema description coverage is 0%, so the description must compensate, but it only says 'bounded' without explaining max_depth, max_entries, or workspace_path. The parameter names are somewhat self-explanatory, but workspace_path semantics in particular—relative vs absolute, default root behavior—are not clarified. The description provides minimal added meaning beyond the schema structure.

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 uses a specific verb ('List') and a specific resource ('bounded live workspace tree'), and the second sentence ('Paths are not bound to a build number') distinguishes it from build-bound artifact or workspace-bundle tools. An agent can tell what this tool does and roughly how it differs from related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'live workspace tree' and 'Paths are not bound to a build number' imply this is for current workspace contents rather than build artifacts or downloaded bundles. However, it never explicitly states when to prefer this tool over alternatives such as jenkins_get_build_artifacts or the workspace bundle download tools.

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

Deploy Server