jenkins-http-mcp-server

jenkins_list_jobs

Read-only

Retrieve a list of Jenkins jobs visible to the authenticated user, including names, URLs, and current status.

Instructions

List jobs visible to the Jenkins user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tree`	No		jobs[name,fullName,url,color,_class]
`depth`	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_list_jobsDictOutput"New value: +"ToolSuccess"

First observedv0.1.0May 6, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds the user-visibility scoping behavior, which tells the agent results are filtered by the authenticated user's Jenkins permissions. No contradiction exists, but the description contributes only modest behavioral context beyond the 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?

Eight words with no filler; the verb and object are front-loaded and every word earns its place. The sentence is appropriately sized for the information it deliberately conveys.

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 output schema and annotations carry the return-value and safety burden, and the tool is low-complexity with two optional parameters. However, the description omits how to control output shape via tree and recursion via depth, and provides no pointer to sibling tools. It is adequate for a simple read-only enumerator but has clear gaps.

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 bears the full burden of explaining the two parameters (tree and depth). It mentions neither. The schema's default value 'jobs[name,fullName,url,color,_class]' hints at the tree format and 'depth' is plausibly self-explanatory, but the description itself adds zero parameter meaning, failing to compensate for the coverage gap.

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?

The description states a specific verb and resource: 'List jobs visible to the Jenkins user.' The phrase 'visible to the Jenkins user' adds meaningful scoping (ACL-filtered results). It is clear, but it does not explicitly differentiate itself from sibling tools such as jenkins_get_job or jenkins_list_views, which keeps it a 4 rather than a 5.

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 given on when to use this tool versus alternatives. The description does not mention when not to use it, when a sibling like jenkins_get_job or jenkins_list_views would be more appropriate, or any prerequisites. The one-line purpose statement only implies usage through its literal meaning.

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

Deploy Server