ado-mcp

ado_get_pipeline

Read-only

Retrieve details of a specific Azure DevOps pipeline using its ID. Use this tool to fetch pipeline configuration and status.

Instructions

Get a single pipeline by ID.

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": {
      "pipelineId": "<pipelineId>"
    },
    "name": "ado_get_pipeline"
  }
}

Input Schema

Name	Required	Description	Default
`project`	No	Project name or ID (defaults to ADO_DEFAULT_PROJECT)
`pipelineId`	Yes	Pipeline ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so read-only behavior is covered. Description adds 'single' cardinality but does not disclose error handling or rate limits, offering minimal value beyond annotations.

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?

Single sentence, no wasted words; perfectly concise for the tool's simplicity.

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?

No output schema exists, but description does not explain return format or behavior (e.g., when pipeline not found). For a simple tool with 2 parameters, it remains incomplete despite annotations.

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 has 100% description coverage for both parameters (project and pipelineId), so baseline is 3. Description adds no extra parameter context beyond what schema provides.

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?

Description 'Get a single pipeline by ID' clearly states the action (get), resource (single pipeline), and identifier (ID), distinguishing it from sibling tools like ado_list_pipelines and ado_get_pipeline_run.

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?

Description provides no guidance on when to use this tool versus alternatives, such as ado_list_pipelines for listing all pipelines, and no mention of prerequisites like project context.

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

Deploy Server