MCP Jenkins

Get View

get_view

Fetch a Jenkins view by path to inspect its jobs and nested sub-views; use / to separate levels and drill down.

Instructions

Get a Jenkins view by path, returning its jobs and/or nested sub-views.

Views can be nested up to multiple levels deep. Use "/" to separate levels in the path. If the view contains sub-views instead of jobs, the response will include their names so you can drill down further.

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": {
      "view_path": "<view_path>"
    },
    "name": "get_view"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	Accepted for compatibility and ignored: views are always returned compact.
`view_path`	Yes	View path using "/" to separate levels. Examples: "All", "frontend", "frontend/nightly". Spaces and special characters in view names are handled automatically.

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

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the nesting model and that responses may contain sub-view names rather than jobs, which is genuine behavioral context, but it omits error behavior for bad paths, whether results are filtered by permissions, and gives no explicit read-only statement.

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?

Three short sentences, front-loaded with the core action, then the nesting/drill-down mechanic. No filler or repetition, though the path-separator sentence duplicates the schema description.

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

Completeness4/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 spelled out, and the tool is a simple two-parameter read. The description covers the one non-obvious aspect (nested sub-views requiring iterative drill-down), leaving only minor gaps like path-resolution failure behavior.

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 coverage is 100%, so the schema already documents both parameters including examples and the fact that depth is ignored. The description's path-format sentence largely restates the schema, and it never mentions the depth parameter's no-op status, so it adds little beyond baseline.

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 a Jenkins view by path") plus the returned payload (jobs and/or nested sub-views). It implicitly differentiates from get_all_views by requiring a path, though it never names that sibling outright.

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?

Gives useful operational context: nested views exist, "/" separates levels, and sub-view names are returned 'so you can drill down further.' However, it never says when to use get_all_views first to discover a path, nor what happens on a nonexistent path.

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