Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

release_get_definitions

Retrieve and filter release definitions by project, search text, tags, or other criteria using Azure DevOps MCP Server with PAT Authentication.

Instructions

Retrieves list of release definitions for a given project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artifactSourceIdNoFilter by artifact source ID
artifactTypeNoFilter by artifact type
continuationTokenNoContinuation token for pagination
definitionIdFilterNoFilter by specific release definition IDs
expandNoExpand options for release definitionsNone
isDeletedNoWhether to include deleted release definitions. Default is false.
isExactNameMatchNoWhether to match the exact name of the release definition. Default is false.
pathNoPath to filter release definitions
projectYesProject ID or name to get release definitions for
propertyFiltersNoFilter by properties associated with the release definitions
queryOrderNoOrder of the resultsNameAscending
searchTextNoSearch text to filter release definitions
searchTextContainsFolderNameNoWhether to include folder names in the search text
tagFilterNoFilter by tags associated with the release definitions
topNoNumber of results to return (for pagination)

Implementation Reference

  • The handler function that implements the core logic of the 'release_get_definitions' tool. It uses the Azure DevOps Release API to fetch release definitions based on the provided parameters and returns the results as a JSON string in the MCP response format.
    async ({
      project,
      searchText,
      expand,
      artifactType,
      artifactSourceId,
      top,
      continuationToken,
      queryOrder,
      path,
      isExactNameMatch,
      tagFilter,
      propertyFilters,
      definitionIdFilter,
      isDeleted,
      searchTextContainsFolderName,
    }) => {
      const connection = await connectionProvider();
      const releaseApi = await connection.getReleaseApi();
      const releaseDefinitions = await releaseApi.getReleaseDefinitions(
        project,
        searchText,
        safeEnumConvert(ReleaseDefinitionExpands, expand),
        artifactType,
        artifactSourceId,
        top,
        continuationToken,
        safeEnumConvert(ReleaseDefinitionQueryOrder, queryOrder),
        path,
        isExactNameMatch,
        tagFilter,
        propertyFilters,
        definitionIdFilter,
        isDeleted,
        searchTextContainsFolderName
      );
    
      return {
        content: [{ type: "text", text: JSON.stringify(releaseDefinitions, null, 2) }],
      };
    }
  • The Zod input schema defining all parameters for the 'release_get_definitions' tool, including project, filters, pagination, and ordering options.
    {
      project: z.string().describe("Project ID or name to get release definitions for"),
      searchText: z.string().optional().describe("Search text to filter release definitions"),
      expand: z
        .enum(getEnumKeys(ReleaseDefinitionExpands) as [string, ...string[]])
        .default("None")
        .describe("Expand options for release definitions"),
      artifactType: z.string().optional().describe("Filter by artifact type"),
      artifactSourceId: z.string().optional().describe("Filter by artifact source ID"),
      top: z.number().optional().describe("Number of results to return (for pagination)"),
      continuationToken: z.string().optional().describe("Continuation token for pagination"),
      queryOrder: z
        .enum(getEnumKeys(ReleaseDefinitionQueryOrder) as [string, ...string[]])
        .default("NameAscending")
        .describe("Order of the results"),
      path: z.string().optional().describe("Path to filter release definitions"),
      isExactNameMatch: z.boolean().optional().default(false).describe("Whether to match the exact name of the release definition. Default is false."),
      tagFilter: z.array(z.string()).optional().describe("Filter by tags associated with the release definitions"),
      propertyFilters: z.array(z.string()).optional().describe("Filter by properties associated with the release definitions"),
      definitionIdFilter: z.array(z.string()).optional().describe("Filter by specific release definition IDs"),
      isDeleted: z.boolean().default(false).describe("Whether to include deleted release definitions. Default is false."),
      searchTextContainsFolderName: z.boolean().optional().describe("Whether to include folder names in the search text"),
    },
  • The server.tool call that registers the 'release_get_definitions' tool on the MCP server, specifying the tool name (via RELEASE_TOOLS), description, input schema, and handler function.
    server.tool(
      RELEASE_TOOLS.get_release_definitions,
      "Retrieves list of release definitions for a given project.",
      {
        project: z.string().describe("Project ID or name to get release definitions for"),
        searchText: z.string().optional().describe("Search text to filter release definitions"),
        expand: z
          .enum(getEnumKeys(ReleaseDefinitionExpands) as [string, ...string[]])
          .default("None")
          .describe("Expand options for release definitions"),
        artifactType: z.string().optional().describe("Filter by artifact type"),
        artifactSourceId: z.string().optional().describe("Filter by artifact source ID"),
        top: z.number().optional().describe("Number of results to return (for pagination)"),
        continuationToken: z.string().optional().describe("Continuation token for pagination"),
        queryOrder: z
          .enum(getEnumKeys(ReleaseDefinitionQueryOrder) as [string, ...string[]])
          .default("NameAscending")
          .describe("Order of the results"),
        path: z.string().optional().describe("Path to filter release definitions"),
        isExactNameMatch: z.boolean().optional().default(false).describe("Whether to match the exact name of the release definition. Default is false."),
        tagFilter: z.array(z.string()).optional().describe("Filter by tags associated with the release definitions"),
        propertyFilters: z.array(z.string()).optional().describe("Filter by properties associated with the release definitions"),
        definitionIdFilter: z.array(z.string()).optional().describe("Filter by specific release definition IDs"),
        isDeleted: z.boolean().default(false).describe("Whether to include deleted release definitions. Default is false."),
        searchTextContainsFolderName: z.boolean().optional().describe("Whether to include folder names in the search text"),
      },
      async ({
        project,
        searchText,
        expand,
        artifactType,
        artifactSourceId,
        top,
        continuationToken,
        queryOrder,
        path,
        isExactNameMatch,
        tagFilter,
        propertyFilters,
        definitionIdFilter,
        isDeleted,
        searchTextContainsFolderName,
      }) => {
        const connection = await connectionProvider();
        const releaseApi = await connection.getReleaseApi();
        const releaseDefinitions = await releaseApi.getReleaseDefinitions(
          project,
          searchText,
          safeEnumConvert(ReleaseDefinitionExpands, expand),
          artifactType,
          artifactSourceId,
          top,
          continuationToken,
          safeEnumConvert(ReleaseDefinitionQueryOrder, queryOrder),
          path,
          isExactNameMatch,
          tagFilter,
          propertyFilters,
          definitionIdFilter,
          isDeleted,
          searchTextContainsFolderName
        );
    
        return {
          content: [{ type: "text", text: JSON.stringify(releaseDefinitions, null, 2) }],
        };
      }
    );
  • src/tools.ts:25-25 (registration)
    Invocation of configureReleaseTools within configureAllTools, which ultimately registers the release tools including 'release_get_definitions'.
    configureReleaseTools(server, tokenProvider, connectionProvider);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a retrieval operation, implying read-only behavior, but doesn't mention any side effects, authentication requirements, rate limits, or pagination details beyond what's in the schema. For a tool with 15 parameters and no annotation coverage, this leaves significant gaps in understanding its behavior.

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 conveys the core purpose without unnecessary words. It's front-loaded with the main action and resource, making it easy to parse quickly. Every word earns its place.

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 tool's complexity (15 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain what a 'release definition' is, how results are structured, or any behavioral nuances like pagination or filtering logic. For a list-retrieval tool with many options, 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%, meaning all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond stating it retrieves 'list of release definitions for a given project', which aligns with the schema but doesn't provide extra context. This meets the baseline score when schema coverage is high.

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 list') and resource ('release definitions for a given project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from similar sibling tools like 'build_get_definitions' or 'release_get_releases', which would require mentioning what distinguishes release definitions from other types of definitions or releases.

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, such as needing project access, or compare it to sibling tools like 'release_get_releases' or 'build_get_definitions' to help the agent choose appropriately. Usage is implied only by the tool name and description.

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