Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

Read Managed File

read_managed_file

Read-onlyIdempotent

Retrieve a Jenkins managed configuration file, such as settings.xml or .npmrc, with secrets masked; specify a folder to read folder-scoped files or omit it for global files.

Instructions

Content of a Config File Provider managed file (settings.xml, .npmrc, properties...) with secrets masked. Global files by default; pass folder= for files defined in a folder.

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": {
      "id": "<id>"
    },
    "name": "read_managed_file"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Managed file id (fileId / settingsConfigId) as shown by get_job_config
`folder`	No	Folder that defines the file; empty = global (Manage Jenkins > Managed files)
`instance`	No	Jenkins instance name from list_instances. Empty = default instance.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new context: secrets are masked in the returned content, and the global-vs-folder resolution default. That is useful beyond what the structured fields convey.

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?

Two tight sentences, front-loaded with what is returned and the masking guarantee before the folder scoping note. The parenthetical file-type examples earn their space by making the resource concrete; there is no filler.

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-shape explanation is unnecessary, and the three params are fully documented in the schema. With read-only annotations plus the explicit secrets-masking and default-scope notes, an agent has enough to call this correctly; only cross-tool routing guidance is absent.

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%, so all three parameters are already documented, including the empty-default semantics for folder and instance. The description's 'Global files by default; pass folder=...' restates the folder default and adds the id provenance hint, but nothing more — baseline 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?

Names a specific verb+resource ('Content of a Config File Provider managed file') and gives concrete examples of the file types (settings.xml, .npmrc, properties), plus a key behavior (secrets masked). It does not explicitly distinguish itself from read_workspace_file or read_artifact, which is the only gap.

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 description implies usage via 'Global files by default; pass folder= for files defined in a folder' and points to get_job_config as the source of the id. However, it never states when to choose this over sibling read tools such as read_workspace_file or read_artifact, leaving the agent to infer.

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