arcade-azure-devops-mcp

AzureDevops_ListBuildDefinitions

AzureDevops_ListBuildDefinitions

List all build or pipeline definitions in an Azure DevOps project, with optional name filter and top count limit.

Instructions

List build/pipeline definitions in a project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "AzureDevops_ListBuildDefinitions"
  }
}

Input Schema

Name	Required	Description
`top`	No	Maximum number of definitions to return
`name`	No	Filter by definition name
`project`	Yes	Project name or ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.5/5.0

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. It only states 'list' with no mention of pagination limits (despite the 'top' parameter), default behavior, or response shape. It does not contradict any annotation, but fails to disclose behavioral traits.

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, front-loaded sentence with no filler or redundancy.

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?

For a simple list tool, the description is minimal but adequate. However, without an output schema or annotations, it would benefit from mentioning response contents or pagination behavior. The 'top' parameter hints at pagination but the description does not explain defaults or result format.

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 baseline is 3. The description adds no additional parameter semantics, but the schema itself documents all three parameters with meaningful descriptions.

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 uses a specific verb 'List' with a clear resource 'build/pipeline definitions' and scoping 'in a project.' It distinguishes itself from the sibling 'ListBuilds' by explicitly referring to definitions rather than builds.

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 the tool is for listing definitions in a project, but provides no explicit guidance on when to use it over alternatives like ListBuilds, nor any conditions or exclusions.

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