Skip to main content
Glama
Jenkins MCP Server

Jenkins MCP Server

by TelmanH

Find Jobs By Scm

find_jobs_by_scm
Read-onlyIdempotent

Find Jenkins jobs across instances whose last build checked out a given repository URL or org/repo fragment, with normalized https, SSH, port, and .git spellings.

Instructions

Jobs whose last build checked out a repository (app repo or Shared Library), across instances: 'job | STATUS #n | repo URL'. URL spellings are normalized (https / ssh / port / Bitbucket /scm/ / .git). ~1 request per instance. Jobs that were never built cannot be found this way.

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": {
      "url": "<url>"
    },
    "name": "find_jobs_by_scm"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRepository URL in any spelling (https, ssh, with .git) or a part of it like 'org/repo'
folderNo
instanceNoInstance name or 'all'all

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds real behavioral context beyond them: URL normalization across https/ssh/port/Bitbucket /scm/ / .git spellings, a cost signal ('~1 request per instance'), and the never-built limitation. These are exactly the traits an agent needs to predict results and cost.

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 compact sentences with the core definition first, then output shape, then caveat. Slightly telegraphic ('across instances:' fragment) but no sentence is padding.

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?

With an output schema present and annotations covering safety, the description supplies the remaining essentials: result format, normalization behavior, request cost, and a key negative constraint. Only the undocumented 'folder' parameter leaves a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, with url and instance documented in the schema. The description adds meaning the schema lacks: the URL is normalized across spellings, so partial forms ('org/repo') behave predictably, and 'across instances' clarifies the semantics of instance='all'. The 'folder' parameter remains unaddressed.

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?

States a precise verb+resource (jobs whose last build checked out a repository) and adds scope qualifiers ('app repo or Shared Library', 'across instances') that clearly differentiate it from sibling list_jobs/get_job. An agent can pick this tool without opening the schema.

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

Usage Guidelines4/5

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

The description implies the use case (locate jobs by repository URL) and gives an explicit exclusion: 'Jobs that were never built cannot be found this way.' It stops short of naming the alternative tool (list_jobs) for jobs without builds, so it is strong but not fully prescriptive.

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