Skip to main content
Glama

getBuild

Retrieve detailed information about specific Jenkins builds, including status, parameters, and artifacts, to monitor and analyze build execution.

Instructions

Get information about a specific build or the last build

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobFullNameYesFull path of the Jenkins job
buildNumberNoBuild number (optional, defaults to last build)

Implementation Reference

  • The main handler function that retrieves information about a specific Jenkins build or the last build using the Jenkins API.
    export async function getBuild(client, args) {
    	const { jobFullName, buildNumber = null } = args;
    	if (!jobFullName) return failure("getBuild", "jobFullName is required");
    	const jobPath = encodeJobPath(jobFullName);
    	const buildPath = buildNumber || "lastBuild";
    
    	try {
    		const response = await client.get(
    			`/job/${jobPath}/${buildPath}/api/json`
    		);
    		if (response.status === 200) {
    			return success("getBuild", { build: response.data });
    		}
    		return failure(
    			"getBuild",
    			`Build not found: ${jobFullName}#${buildPath}`,
    			{ statusCode: response.status }
    		);
    	} catch (error) {
    		return formatError(error, "getBuild");
    	}
  • Tool registration in the central registry, including input schema and handler reference. Used by getAllTools() for MCP server.
    getBuild: {
    	name: "getBuild",
    	description: "Get information about a specific build or the last build",
    	inputSchema: {
    		type: "object",
    		properties: {
    			jobFullName: {
    				type: "string",
    				description: "Full path of the Jenkins job",
    			},
    			buildNumber: {
    				type: "integer",
    				description:
    					"Build number (optional, defaults to last build)",
    			},
    		},
    		required: ["jobFullName"],
    	},
    	handler: getBuild,
    },
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 required permissions, rate limits, error handling, or what specific information is returned (e.g., status, logs, metadata). This is a significant gap 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 function without any wasted words. It's front-loaded and appropriately sized for its purpose, earning full marks for conciseness.

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 the complexity of build information retrieval, no annotations, and no output schema, the description is incomplete. It doesn't explain what information is returned (e.g., build status, duration, artifacts), potential side effects, or error cases, leaving the agent with insufficient context for effective use.

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 the schema already documents both parameters fully. The description adds minimal value beyond the schema by implying the tool can fetch 'the last build' if buildNumber is omitted, but this is already covered in the schema's description for buildNumber. Baseline 3 is appropriate as the schema does the heavy lifting.

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 specific build or the last build'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'getJob' or 'getStatus', which might also retrieve build-related information, so it doesn't reach the highest score.

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 'getJob' (which might include build info) and 'getStatus' (which could be similar), there's no indication of context, prerequisites, or exclusions, leaving usage unclear.

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