Skip to main content
Glama
nikydobrev

Azure DevOps Multi-Organization MCP Server

by nikydobrev

pipelines_get_build_definition_revisions

Retrieve revision history for Azure DevOps build definitions to track changes, audit modifications, and restore previous configurations.

Instructions

Gets the revision history of a build definition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesThe name of the Azure DevOps organization
projectYesProject ID or name to get the build definition revisions for
definitionIdYesID of the build definition to get revisions for

Implementation Reference

  • The inline handler function that executes the tool: connects to Azure DevOps, gets Build API, fetches definition revisions for the given project and definitionId, and returns JSON stringified response.
    async ({ organization, project, definitionId }) => {
        const connection = await connectionManager.getConnection(organization);
        const buildApi = await connection.getBuildApi();
        const revisions = await buildApi.getDefinitionRevisions(project, definitionId);
        return {
            content: [{ type: "text", text: JSON.stringify(revisions, null, 2) }],
        };
    }
  • Input schema using Zod for validating parameters: organization, project, definitionId.
    {
        organization: z.string().describe("The name of the Azure DevOps organization"),
        project: z.string().describe("Project ID or name to get the build definition revisions for"),
        definitionId: z.number().describe("ID of the build definition to get revisions for"),
    },
  • Registration of the tool with McpServer.tool(), including name, description, schema, and handler.
    server.tool(
      "pipelines_get_build_definition_revisions",
      "Gets the revision history of a build definition",
      {
          organization: z.string().describe("The name of the Azure DevOps organization"),
          project: z.string().describe("Project ID or name to get the build definition revisions for"),
          definitionId: z.number().describe("ID of the build definition to get revisions for"),
      },
      async ({ organization, project, definitionId }) => {
          const connection = await connectionManager.getConnection(organization);
          const buildApi = await connection.getBuildApi();
          const revisions = await buildApi.getDefinitionRevisions(project, definitionId);
          return {
              content: [{ type: "text", text: JSON.stringify(revisions, 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. While 'Gets' implies a read-only operation, it doesn't specify authentication requirements, rate limits, pagination behavior, or what format the revision history returns. For a tool with zero annotation coverage, this leaves significant gaps.

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 with zero wasted words. It's appropriately sized for a straightforward retrieval tool and front-loads the core purpose immediately.

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 tool's moderate complexity (retrieving revision history), lack of annotations, and no output schema, the description is minimally adequate but incomplete. It states what the tool does but omits behavioral details and output expectations that would help an agent use it correctly.

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 all three parameters (organization, project, definitionId). The description doesn't add any additional meaning about these parameters beyond what the schema provides, meeting the baseline for high 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 verb ('Gets') and resource ('revision history of a build definition'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'pipelines_get_build_definitions' or 'pipelines_get_build_changes', which prevents a perfect 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. There are multiple sibling tools for retrieving build-related information (e.g., 'pipelines_get_build_definitions', 'pipelines_get_builds'), but no indication of when revision history is needed versus other build data.

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/nikydobrev/mcp-server-azure-devops-multi'

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