Azure DevOps MCP Server

Get last build status

get_last_build

Retrieve the status and result of the most recent build in a project. Optionally filter by pipeline name to check a specific pipeline's last run.

Instructions

Get the status and result of the most recent build in a project. Use this to answer questions like 'what is the last pipeline status?', 'did the last build succeed?', 'what ran last?'. Optionally filter by pipeline name (partial match). Returns: buildNumber, status (inProgress/completed), result (succeeded/failed/partiallySucceeded/canceled), pipeline name, branch, who triggered it, and start/finish time.

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": "get_last_build"
  }
}

Input Schema

Name	Required	Description	Default
`project`	No	Azure DevOps project name or id. Defaults to AZDO_PROJECT if set.
`pipelineName`	No	Filter by pipeline name (partial, case-insensitive). Omit to get the last build across all pipelines.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that it's a read operation returning specific fields (buildNumber, status, result, etc.) and mentions partial matching on pipeline. Missing details on rate limits or authentication, but adequate for a simple read tool.

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 four sentences with clear flow: action, usage examples, filtering option, return fields. No redundant information, though the question list could be shortened. Overall efficient for the purpose.

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

Completeness4/5

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

For a simple read tool with two optional parameters and no output schema, the description covers purpose, usage, and return fields. It does not elaborate on status/result enum values, but that is minor. Adequate for selecting and invoking the tool.

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%, so baseline is 3. The description adds no significant information beyond the schema descriptions; it merely repeats them. Thus, it meets the baseline but does not exceed it.

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 it retrieves the most recent build status and result. It specifies the resource (last build in a project) and verb (get). This distinguishes it from siblings like 'list_builds' (list all) and 'get_build' (specific build).

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

Usage Guidelines4/5

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

The description provides example questions and notes optional pipeline filtering. However, it does not explicitly state when not to use this tool versus alternatives like 'get_build' for specific builds or 'list_builds' for multiple builds, leaving some ambiguity.

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

Deploy Server