Azure DevOps MCP Server

download_pipeline_artifact

Download a file from a pipeline run artifact by run ID and artifact path, then return its textual content for inspection or parsing.

Instructions

Download a file from a pipeline run artifact and return its textual content

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": {
      "runId": "<runId>",
      "artifactPath": "<artifactPath>"
    },
    "name": "download_pipeline_artifact"
  }
}

Input Schema

Name	Required	Description
`runId`	Yes	Pipeline run identifier
`projectId`	No	The ID or name of the project (Default: MyProject)
`pipelineId`	No	Optional guard; validates the run belongs to this pipeline
`artifactPath`	Yes	Path to the desired file inside the artifact (format: <artifactName>/<path/to/file>)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.6Sep 30, 2026
- addedInput schema / properties / pipelineId / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / runId / maximum
```
Added value: +9007199254740991
```
Addedv1.0.0Jan 2, 2026

TDQS

B3.2/5.0

Behavior3/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 usefully discloses the return shape (textual content, implying non-text/binary artifacts are not supported), but it omits access requirements, size limits, and failure behavior for missing paths.

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?

A single front-loaded sentence with no filler; every clause earns its place. It is appropriately sized, though it could have spent one more sentence on routing guidance without becoming bloated.

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 4-parameter read tool with no annotations and no output schema, the description covers the core action and return type but leaves out routing versus siblings and error/limit behavior. It is minimally viable rather than complete.

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 runId, projectId, pipelineId, and artifactPath are all documented in the schema, including the artifactPath format and the pipelineId guard semantics. The description adds no additional parameter meaning, so the baseline 3 applies.

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?

States a specific verb (download) plus resource (pipeline run artifact) and clarifies the return is textual content. It distinguishes the artifact source from repo-level fetches, though it does not name the closest sibling (get_file_content) to make the boundary explicit.

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 statement of when to prefer this over get_file_content, get_pipeline_log, or get_pipeline_run, and no prerequisites such as run status or permissions are mentioned. The agent must infer usage entirely from the name and schema.

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

Deploy Server