Skip to main content
Glama
jfrog

JFrog MCP Server

Official
by jfrog

jfrog_get_specific_build

Retrieve detailed information for a specific build by name, with optional project scoping, using the JFrog MCP Server’s API capabilities.

Instructions

Get details for a specific build by name, optionally scoped to a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buildNameYesName of the build to retrieve
projectNoOptional project key to scope the build search

Implementation Reference

  • Core function implementing the tool logic: constructs the JFrog API URL for the specific build, makes a GET request using jfrogRequest, and parses the response with the output schema.
    export async function getSpecificBuild(buildName: string, project?: string) {
      const url = project 
        ? `/artifactory/api/build/${buildName}?project=${project}`
        : `/artifactory/api/build/${buildName}`;
    
      const response = await jfrogRequest(url, {
        method: "GET",
      });
         
      return buildsSchemas.JFrogBuildDetailsSchema.parse(response);
    }
  • Zod input schema for the tool, defining buildName (required) and project (optional).
    export const GetSpecificBuildSchema = z.object({
      buildName: z.string().describe("Name of the build to retrieve"),
      project: z.string().optional().describe("Optional project key to scope the build search")
    });
  • tools/builds.ts:32-41 (registration)
    Local registration of the tool: defines name, description, input schema, and handler wrapper that parses args and delegates to getSpecificBuild.
    const getSpecificBuildTool = {
      name: "jfrog_get_specific_build",
      description: "Get details for a specific build by name, optionally scoped to a project",
      inputSchema: zodToJsonSchema(buildsSchemas.GetSpecificBuildSchema),
      //outputSchema: zodToJsonSchema(buildsSchemas.JFrogBuildDetailsSchema),
      handler: async (args: any) => {
        const parsedArgs = buildsSchemas.GetSpecificBuildSchema.parse(args);
        return await getSpecificBuild(parsedArgs.buildName, parsedArgs.project);
      }
    };
  • tools/index.ts:13-23 (registration)
    Global registration: imports BuildsTools (containing jfrog_get_specific_build) and spreads it into the main tools array exported for use.
    export const tools =[
      ...RepositoryTools,
      ...BuildsTools,
      ...RuntimeTools,
      ...AccessTools,
      ...AQLTools,
      ...CatalogTools,
      ...CurationTools,
      ...PermissionsTools,
      ...ArtifactSecurityTools,
    ];
  • Output schema used to parse the JFrog API response for build details.
    export const JFrogBuildDetailsSchema = z.object({
      uri: z.string(),
      buildsNumbers: z.array(z.object({
        uri: z.string(),
        started: z.string().describe("Build start timestamp in ISO8601 format")
      }))
    });

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/jfrog/mcp-jfrog'

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