Skip to main content
Glama

getJob

Retrieve detailed information about a specific Jenkins job, including its configuration, status, and build history, to monitor and manage automation workflows.

Instructions

Get information about a Jenkins job

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobFullNameYesFull path of the Jenkins job

Implementation Reference

  • The handler function that implements the core logic for the 'getJob' tool. It retrieves information about a specific Jenkins job by making an API call to `/job/{jobPath}/api/json`.
    export async function getJob(client, args) {
    	const { jobFullName } = args;
    	if (!jobFullName) return failure("getJob", "jobFullName is required");
    	const jobPath = encodeJobPath(jobFullName);
    
    	try {
    		const response = await client.get(`/job/${jobPath}/api/json`);
    		if (response.status === 200) {
    			return success("getJob", { job: response.data });
    		}
    		return failure("getJob", `Job not found: ${jobFullName}`, {
    			statusCode: response.status,
    		});
    	} catch (error) {
    		return formatError(error, "getJob");
    	}
    }
  • The registration entry for the 'getJob' tool in the central tool registry, including name, description, input schema, and reference to the handler function.
    getJob: {
    	name: "getJob",
    	description: "Get information about a Jenkins job",
    	inputSchema: {
    		type: "object",
    		properties: {
    			jobFullName: {
    				type: "string",
    				description: "Full path of the Jenkins job",
    			},
    		},
    		required: ["jobFullName"],
    	},
    	handler: getJob,
    },
  • The input schema definition for the 'getJob' tool, specifying the required 'jobFullName' parameter.
    inputSchema: {
    	type: "object",
    	properties: {
    		jobFullName: {
    			type: "string",
    			description: "Full path of the Jenkins job",
    		},
    	},
    	required: ["jobFullName"],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'gets information' but doesn't disclose behavioral traits such as whether it's read-only, what permissions are needed, rate limits, or the format of returned information. This is inadequate for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned, error conditions, or behavioral details. For a tool with one parameter but missing structured context, it should provide more guidance to be fully helpful.

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%, with the parameter 'jobFullName' documented as 'Full path of the Jenkins job'. The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the verb ('Get') and resource ('information about a Jenkins job'), making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'getBuild' or 'getJobs', which also retrieve job-related information, so it misses full differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'getBuild' (for specific builds) and 'getJobs' (for listing jobs), there's no indication of context, prerequisites, or exclusions, leaving usage ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/umishra1504/Jenkins-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server