Azure DevOps MCP Server

List builds

list_builds

Retrieve recent builds from an Azure DevOps project, with optional filters for pipeline, definition, status, and count.

Instructions

List recent builds in a project, optionally filtered by pipeline/definition.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_builds"
  }
}

Input Schema

Name	Required	Description
`project`	No	Azure DevOps project name or id. Defaults to AZDO_PROJECT if set.
`definitionId`	No	Filter by pipeline/definition id.
`top`	No	Max builds to return.
`statusFilter`	No	Filter by build status.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the action without disclosing any side effects, permissions, rate limits, or return format. For a read operation, this is minimal but not harmful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no unnecessary words. It is front-loaded with the core action. However, it could benefit from slightly more structure, such as noting that it is read-only.

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?

With no output schema and limited annotations, the description does not fully inform the agent about return values, ordering, or pagination behavior. For a tool that returns a list, more context is needed for correct usage.

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 coverage is 100%, with each parameter already described in the input schema. The description does not add new meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists builds in a project, with optional filtering. It uses a specific verb ('List') and resource ('builds'), and the mention of filtering by pipeline/definition distinguishes it from siblings like get_build or get_last_build.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing builds with optional filters, but provides no explicit guidance on when to use this tool over alternatives like list_failed_builds or get_last_build. No when-not-to-use or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server