Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_pipeline_runs

Retrieve recent pipeline runs by pipeline ID and filter by state, branch, result, or creation date; sort and paginate results to track builds.

Instructions

List recent runs for a pipeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYesMaximum number of runs to return (1-100)
stateNoFilter by current run state
branchNoBranch to filter by (e.g., "main" or "refs/heads/main")
resultNoFilter by final run result
orderByYesSort order for run creation datecreatedDate desc
createdToNoFilter runs created at or before this time (ISO 8601)
projectIdNoThe ID or name of the project (Default: MyProject)
pipelineIdYesPipeline numeric ID
createdFromNoFilter runs created at or after this time (ISO 8601)
continuationTokenNoContinuation token for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.6
    • addedInput schema / properties / createdFrom / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • addedInput schema / properties / createdTo / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • addedInput schema / properties / pipelineId / maximum
      Added value: +9007199254740991
    • changedInput schema / required
      Previous value: -[
-  "pipelineId"
-]New value: +[
+  "pipelineId",
+  "top",
+  "orderBy"
+]
  2. Addedv1.0.0

TDQS

C2.9/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 behavioral burden. It does not disclose that this is a read-only listing operation, nor does it mention pagination via continuationToken, default ordering, or the default limit of 50 runs.

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 front-loaded sentence with no wasted words. It is appropriately concise, though it could be slightly more informative without becoming verbose.

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?

For a 10-parameter tool with no annotations and no output schema, the description is too thin. It omits key context such as pagination behavior, default sorting, and how it relates to sibling run-retrieval tools.

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 all 10 parameters are already documented in the schema. The description adds no parameter meaning beyond the schema baseline, which is appropriate for a score of 3.

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 states a specific verb and resource: list recent runs for a pipeline. It is clear what the tool does, but it does not distinguish itself from siblings like get_pipeline_run or pipeline_timeline, which also deal with pipeline runs.

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?

There is no guidance on when to use this tool instead of get_pipeline_run, pipeline_timeline, get_pipeline_log, or list_pipelines. The description implies a listing use case but provides no explicit context or exclusions.

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

Deploy Server

Other Tools