Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

build_get_builds

Fetch and filter build data from Azure DevOps projects using criteria like build ID, status, branch, or requester. Ideal for tracking and analyzing build history.

Instructions

Retrieves a list of builds for a given project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchNameNoBranch name to filter builds
buildIdsNoArray of build IDs to retrieve
buildNumberNoBuild number to filter builds
continuationTokenNoToken for continuing paged results
definitionsNoArray of build definition IDs to filter builds
deletedFilterNoFilter for deleted builds (see QueryDeletedOption enum)
maxBuildsPerDefinitionNoMaximum number of builds per definition
maxTimeNoMaximum finish time to filter builds
minTimeNoMinimum finish time to filter builds
projectYesProject ID or name to get builds for
propertiesNoArray of property names to include in the results
queryOrderNoOrder in which builds are returnedQueueTimeDescending
queuesNoArray of queue IDs to filter builds
reasonFilterNoReason filter for the build (see BuildReason enum)
repositoryIdNoRepository ID to filter builds
repositoryTypeNoType of repository to filter builds
requestedForNoUser ID or name who requested the build
resultFilterNoResult filter for the build (see BuildResult enum)
statusFilterNoStatus filter for the build (see BuildStatus enum)
tagFiltersNoArray of tags to filter builds
topNoMaximum number of builds to return

Implementation Reference

  • Handler function that fetches builds from Azure DevOps using the Build API based on provided filters and returns JSON-formatted results.
    async ({
      project,
      definitions,
      queues,
      buildNumber,
      minTime,
      maxTime,
      requestedFor,
      reasonFilter,
      statusFilter,
      resultFilter,
      tagFilters,
      properties,
      top,
      continuationToken,
      maxBuildsPerDefinition,
      deletedFilter,
      queryOrder,
      branchName,
      buildIds,
      repositoryId,
      repositoryType,
    }) => {
      const connection = await connectionProvider();
      const buildApi = await connection.getBuildApi();
      const builds = await buildApi.getBuilds(
        project,
        definitions,
        queues,
        buildNumber,
        minTime,
        maxTime,
        requestedFor,
        reasonFilter,
        statusFilter,
        resultFilter,
        tagFilters,
        properties,
        top,
        continuationToken,
        maxBuildsPerDefinition,
        deletedFilter,
        safeEnumConvert(BuildQueryOrder, queryOrder),
        branchName,
        buildIds,
        repositoryId,
        repositoryType
      );
    
      return {
        content: [{ type: "text", text: JSON.stringify(builds, null, 2) }],
      };
    }
  • Zod input schema defining all parameters for querying builds, including project, filters, pagination, and ordering options.
      project: z.string().describe("Project ID or name to get builds for"),
      definitions: z.array(z.number()).optional().describe("Array of build definition IDs to filter builds"),
      queues: z.array(z.number()).optional().describe("Array of queue IDs to filter builds"),
      buildNumber: z.string().optional().describe("Build number to filter builds"),
      minTime: z.coerce.date().optional().describe("Minimum finish time to filter builds"),
      maxTime: z.coerce.date().optional().describe("Maximum finish time to filter builds"),
      requestedFor: z.string().optional().describe("User ID or name who requested the build"),
      reasonFilter: z.number().optional().describe("Reason filter for the build (see BuildReason enum)"),
      statusFilter: z.number().optional().describe("Status filter for the build (see BuildStatus enum)"),
      resultFilter: z.number().optional().describe("Result filter for the build (see BuildResult enum)"),
      tagFilters: z.array(z.string()).optional().describe("Array of tags to filter builds"),
      properties: z.array(z.string()).optional().describe("Array of property names to include in the results"),
      top: z.number().optional().describe("Maximum number of builds to return"),
      continuationToken: z.string().optional().describe("Token for continuing paged results"),
      maxBuildsPerDefinition: z.number().optional().describe("Maximum number of builds per definition"),
      deletedFilter: z.number().optional().describe("Filter for deleted builds (see QueryDeletedOption enum)"),
      queryOrder: z
        .enum(getEnumKeys(BuildQueryOrder) as [string, ...string[]])
        .default("QueueTimeDescending")
        .optional()
        .describe("Order in which builds are returned"),
      branchName: z.string().optional().describe("Branch name to filter builds"),
      buildIds: z.array(z.number()).optional().describe("Array of build IDs to retrieve"),
      repositoryId: z.string().optional().describe("Repository ID to filter builds"),
      repositoryType: z.enum(["TfsGit", "GitHub", "BitbucketCloud"]).optional().describe("Type of repository to filter builds"),
    },
  • MCP server.tool registration call that registers the 'build_get_builds' tool with its description, input schema, and handler function.
    server.tool(
      BUILD_TOOLS.get_builds,
      "Retrieves a list of builds for a given project.",
      {
        project: z.string().describe("Project ID or name to get builds for"),
        definitions: z.array(z.number()).optional().describe("Array of build definition IDs to filter builds"),
        queues: z.array(z.number()).optional().describe("Array of queue IDs to filter builds"),
        buildNumber: z.string().optional().describe("Build number to filter builds"),
        minTime: z.coerce.date().optional().describe("Minimum finish time to filter builds"),
        maxTime: z.coerce.date().optional().describe("Maximum finish time to filter builds"),
        requestedFor: z.string().optional().describe("User ID or name who requested the build"),
        reasonFilter: z.number().optional().describe("Reason filter for the build (see BuildReason enum)"),
        statusFilter: z.number().optional().describe("Status filter for the build (see BuildStatus enum)"),
        resultFilter: z.number().optional().describe("Result filter for the build (see BuildResult enum)"),
        tagFilters: z.array(z.string()).optional().describe("Array of tags to filter builds"),
        properties: z.array(z.string()).optional().describe("Array of property names to include in the results"),
        top: z.number().optional().describe("Maximum number of builds to return"),
        continuationToken: z.string().optional().describe("Token for continuing paged results"),
        maxBuildsPerDefinition: z.number().optional().describe("Maximum number of builds per definition"),
        deletedFilter: z.number().optional().describe("Filter for deleted builds (see QueryDeletedOption enum)"),
        queryOrder: z
          .enum(getEnumKeys(BuildQueryOrder) as [string, ...string[]])
          .default("QueueTimeDescending")
          .optional()
          .describe("Order in which builds are returned"),
        branchName: z.string().optional().describe("Branch name to filter builds"),
        buildIds: z.array(z.number()).optional().describe("Array of build IDs to retrieve"),
        repositoryId: z.string().optional().describe("Repository ID to filter builds"),
        repositoryType: z.enum(["TfsGit", "GitHub", "BitbucketCloud"]).optional().describe("Type of repository to filter builds"),
      },
      async ({
        project,
        definitions,
        queues,
        buildNumber,
        minTime,
        maxTime,
        requestedFor,
        reasonFilter,
        statusFilter,
        resultFilter,
        tagFilters,
        properties,
        top,
        continuationToken,
        maxBuildsPerDefinition,
        deletedFilter,
        queryOrder,
        branchName,
        buildIds,
        repositoryId,
        repositoryType,
      }) => {
        const connection = await connectionProvider();
        const buildApi = await connection.getBuildApi();
        const builds = await buildApi.getBuilds(
          project,
          definitions,
          queues,
          buildNumber,
          minTime,
          maxTime,
          requestedFor,
          reasonFilter,
          statusFilter,
          resultFilter,
          tagFilters,
          properties,
          top,
          continuationToken,
          maxBuildsPerDefinition,
          deletedFilter,
          safeEnumConvert(BuildQueryOrder, queryOrder),
          branchName,
          buildIds,
          repositoryId,
          repositoryType
        );
    
        return {
          content: [{ type: "text", text: JSON.stringify(builds, null, 2) }],
        };
      }
    );
  • Constant object mapping tool names to their string identifiers, including 'get_builds: "build_get_builds"'.
    const BUILD_TOOLS = {
      get_definitions: "build_get_definitions",
      get_definition_revisions: "build_get_definition_revisions",
      get_builds: "build_get_builds",
      get_log: "build_get_log",
      get_log_by_id: "build_get_log_by_id",
      get_changes: "build_get_changes",
      run_build: "build_run_build",
      get_status: "build_get_status",
      update_build_stage: "build_update_build_stage",
    };
  • src/tools.ts:19-30 (registration)
    Top-level function that configures all tools by calling configureBuildTools among others, which indirectly registers the build tools.
    function configureAllTools(server: McpServer, tokenProvider: () => Promise<AccessToken>, connectionProvider: () => Promise<WebApi>, userAgentProvider: () => string) {
      configureCoreTools(server, tokenProvider, connectionProvider, userAgentProvider);
      configureWorkTools(server, tokenProvider, connectionProvider);
      configureBuildTools(server, tokenProvider, connectionProvider, userAgentProvider);
      configureRepoTools(server, tokenProvider, connectionProvider, userAgentProvider);
      configureWorkItemTools(server, tokenProvider, connectionProvider, userAgentProvider);
      configureReleaseTools(server, tokenProvider, connectionProvider);
      configureWikiTools(server, tokenProvider, connectionProvider);
      configureTestPlanTools(server, tokenProvider, connectionProvider);
      configureSearchTools(server, tokenProvider, connectionProvider, userAgentProvider);
      configureAdvSecTools(server, tokenProvider, connectionProvider);
    }
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 of behavioral disclosure. It states it 'retrieves a list,' implying a read-only operation, but doesn't cover critical aspects like pagination behavior (implied by 'continuationToken' in schema), rate limits, authentication needs, or what the returned list structure looks like. For a tool with 21 parameters and no annotations, this is a significant gap in transparency.

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 any wasted words. It's 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 the complexity (21 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain the return format, pagination, filtering logic, or error handling. For a list-retrieval tool with many optional filters, more context is needed to guide 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?

The schema description coverage is 100%, with detailed descriptions for all 21 parameters, so the schema does the heavy lifting. The description adds no additional parameter semantics beyond implying a list retrieval, which is already clear from the schema. This meets the baseline for high schema coverage.

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 action ('Retrieves') and resource ('list of builds for a given project'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'build_get_status' or 'build_get_changes', which might also involve retrieving build-related information, so it lacks specific sibling distinction.

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. It doesn't mention any prerequisites, exclusions, or compare it to other build-related tools in the sibling list, leaving the agent with no contextual usage information.

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

Related 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/ennuiii/DevOpsMcpPAT'

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