MCP Jenkins

Get Build Artifact Url

get_build_artifact_url

Retrieve the direct URL for an artifact from a specific Jenkins build using the job name and relative path; optionally specify a build number or use the last build.

Instructions

Get the direct URL of an artifact from a specific build in Jenkins

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": {
      "fullname": "<fullname>",
      "relative_path": "<relative_path>"
    },
    "name": "get_build_artifact_url"
  }
}

Input Schema

Name	Required	Description
`number`	No	The number of the build, if None, get the last build
`fullname`	Yes	The fullname of the job
`relative_path`	Yes	The relative path of the artifact (e.g. playwright-report/index.html)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0+microtech.5Nov 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only lookup but says nothing about whether the returned URL is authenticated, expiring, or shareable, nor what happens if the artifact does not exist or the build number is omitted. For a tool whose output is a URL other agents may follow, this is a meaningful gap.

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?

A single well-formed sentence with the resource and scope front-loaded and no wasted wording. Brevity is appropriate, though one additional clause about the URL's nature would have earned its place.

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 tool is simple, parameters are fully documented, and an output schema exists so return values need not be explained. However, with zero annotations the definition should say more about ordering against get_build_artifact and about the returned URL's usability.

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%, including a description for the optional 'number' default of last build and the relative_path example, so the schema does the heavy lifting. The description only restates that the artifact belongs to a specific build and adds no format or path syntax meaning beyond the schema.

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 the direct URL of an artifact') and scopes it to 'a specific build in Jenkins', so the agent knows it returns a URL rather than artifact content. It stops short of naming the closely related sibling get_build_artifact, leaving the URL-vs-content distinction to inference.

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?

There is no explicit when-to-use guidance, no exclusion, and no named alternative. The agent must guess whether to call this versus get_build_artifact or get_all_build_artifacts when it needs artifact information.

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