Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

build_get_definitions

Retrieve a filtered list of build definitions for a specific project in Azure DevOps, enabling efficient management and querying of build configurations based on criteria like repository type, name, path, or build activity.

Instructions

Retrieves a list of build definitions for a given project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
builtAfterNoReturn definitions that have builds after this date
continuationTokenNoToken for continuing paged results
definitionIdsNoArray of build definition IDs to filter
includeAllPropertiesNoWhether to include all properties in the results
includeLatestBuildsNoWhether to include the latest builds for each definition
minMetricsTimeNoMinimum metrics time to filter build definitions
nameNoName of the build definition to filter
notBuiltAfterNoReturn definitions that do not have builds after this date
pathNoPath of the build definition to filter
processTypeNoProcess type to filter build definitions
projectYesProject ID or name to get build definitions for
queryOrderNoOrder in which build definitions are returned
repositoryIdNoRepository ID to filter build definitions
repositoryTypeNoType of repository to filter build definitions
taskIdFilterNoTask ID to filter build definitions
topNoMaximum number of build definitions to return
yamlFilenameNoYAML filename to filter build definitions

Implementation Reference

  • BUILD_TOOLS constant mapping internal names to MCP tool names, including 'get_definitions' to 'build_get_definitions'.
    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",
    };
  • Zod input schema for the build_get_definitions tool defining parameters for querying build definitions.
    {
      project: z.string().describe("Project ID or name to get build definitions for"),
      repositoryId: z.string().optional().describe("Repository ID to filter build definitions"),
      repositoryType: z.enum(["TfsGit", "GitHub", "BitbucketCloud"]).optional().describe("Type of repository to filter build definitions"),
      name: z.string().optional().describe("Name of the build definition to filter"),
      path: z.string().optional().describe("Path of the build definition to filter"),
      queryOrder: z
        .enum(getEnumKeys(DefinitionQueryOrder) as [string, ...string[]])
        .optional()
        .describe("Order in which build definitions are returned"),
      top: z.number().optional().describe("Maximum number of build definitions to return"),
      continuationToken: z.string().optional().describe("Token for continuing paged results"),
      minMetricsTime: z.coerce.date().optional().describe("Minimum metrics time to filter build definitions"),
      definitionIds: z.array(z.number()).optional().describe("Array of build definition IDs to filter"),
      builtAfter: z.coerce.date().optional().describe("Return definitions that have builds after this date"),
      notBuiltAfter: z.coerce.date().optional().describe("Return definitions that do not have builds after this date"),
      includeAllProperties: z.boolean().optional().describe("Whether to include all properties in the results"),
      includeLatestBuilds: z.boolean().optional().describe("Whether to include the latest builds for each definition"),
      taskIdFilter: z.string().optional().describe("Task ID to filter build definitions"),
      processType: z.number().optional().describe("Process type to filter build definitions"),
      yamlFilename: z.string().optional().describe("YAML filename to filter build definitions"),
    },
  • Handler implementation that uses Azure DevOps Build API to fetch build definitions based on input parameters and returns JSON-formatted results.
    async ({
      project,
      repositoryId,
      repositoryType,
      name,
      path,
      queryOrder,
      top,
      continuationToken,
      minMetricsTime,
      definitionIds,
      builtAfter,
      notBuiltAfter,
      includeAllProperties,
      includeLatestBuilds,
      taskIdFilter,
      processType,
      yamlFilename,
    }) => {
      const connection = await connectionProvider();
      const buildApi = await connection.getBuildApi();
      const buildDefinitions = await buildApi.getDefinitions(
        project,
        name,
        repositoryId,
        repositoryType,
        safeEnumConvert(DefinitionQueryOrder, queryOrder),
        top,
        continuationToken,
        minMetricsTime,
        definitionIds,
        path,
        builtAfter,
        notBuiltAfter,
        includeAllProperties,
        includeLatestBuilds,
        taskIdFilter,
        processType,
        yamlFilename
      );
    
      return {
        content: [{ type: "text", text: JSON.stringify(buildDefinitions, null, 2) }],
      };
    }
  • Registers the 'build_get_definitions' tool with MCP server, specifying description, input schema, and handler function.
    server.tool(
      BUILD_TOOLS.get_definitions,
      "Retrieves a list of build definitions for a given project.",
      {
        project: z.string().describe("Project ID or name to get build definitions for"),
        repositoryId: z.string().optional().describe("Repository ID to filter build definitions"),
        repositoryType: z.enum(["TfsGit", "GitHub", "BitbucketCloud"]).optional().describe("Type of repository to filter build definitions"),
        name: z.string().optional().describe("Name of the build definition to filter"),
        path: z.string().optional().describe("Path of the build definition to filter"),
        queryOrder: z
          .enum(getEnumKeys(DefinitionQueryOrder) as [string, ...string[]])
          .optional()
          .describe("Order in which build definitions are returned"),
        top: z.number().optional().describe("Maximum number of build definitions to return"),
        continuationToken: z.string().optional().describe("Token for continuing paged results"),
        minMetricsTime: z.coerce.date().optional().describe("Minimum metrics time to filter build definitions"),
        definitionIds: z.array(z.number()).optional().describe("Array of build definition IDs to filter"),
        builtAfter: z.coerce.date().optional().describe("Return definitions that have builds after this date"),
        notBuiltAfter: z.coerce.date().optional().describe("Return definitions that do not have builds after this date"),
        includeAllProperties: z.boolean().optional().describe("Whether to include all properties in the results"),
        includeLatestBuilds: z.boolean().optional().describe("Whether to include the latest builds for each definition"),
        taskIdFilter: z.string().optional().describe("Task ID to filter build definitions"),
        processType: z.number().optional().describe("Process type to filter build definitions"),
        yamlFilename: z.string().optional().describe("YAML filename to filter build definitions"),
      },
      async ({
        project,
        repositoryId,
        repositoryType,
        name,
        path,
        queryOrder,
        top,
        continuationToken,
        minMetricsTime,
        definitionIds,
        builtAfter,
        notBuiltAfter,
        includeAllProperties,
        includeLatestBuilds,
        taskIdFilter,
        processType,
        yamlFilename,
      }) => {
        const connection = await connectionProvider();
        const buildApi = await connection.getBuildApi();
        const buildDefinitions = await buildApi.getDefinitions(
          project,
          name,
          repositoryId,
          repositoryType,
          safeEnumConvert(DefinitionQueryOrder, queryOrder),
          top,
          continuationToken,
          minMetricsTime,
          definitionIds,
          path,
          builtAfter,
          notBuiltAfter,
          includeAllProperties,
          includeLatestBuilds,
          taskIdFilter,
          processType,
          yamlFilename
        );
    
        return {
          content: [{ type: "text", text: JSON.stringify(buildDefinitions, null, 2) }],
        };
      }
    );
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 'Retrieves a list' which implies a read-only operation, but doesn't mention pagination behavior (though 'continuationToken' in schema hints at it), rate limits, authentication needs, or what happens with large result sets. This leaves significant gaps for an agent to understand operational constraints.

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, clear sentence that efficiently communicates the core purpose without unnecessary words. It's front-loaded with the essential action and resource, making it easy to parse quickly.

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

Completeness3/5

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

Given the complexity (17 parameters, no output schema, no annotations), the description is minimally adequate. It identifies the resource but doesn't explain return format, error conditions, or relationship to sibling tools. For a list-retrieval tool with many filtering options, more context about typical usage patterns would be 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%, so all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond stating it retrieves 'for a given project' (which aligns with the required 'project' parameter). This meets the baseline for high schema coverage but doesn't provide extra 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 ('Retrieves') and resource ('list of build definitions for a given project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'build_get_definition_revisions' or 'release_get_definitions', which might retrieve similar but different resources.

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 many sibling tools available (e.g., 'build_get_definition_revisions', 'release_get_definitions'), there's no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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