Skip to main content
Glama
Sign In
Azure DevOps MCP Server

Azure DevOps MCP Server

by jafarimohammad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List pipelines

list_pipelines

Retrieve all pipelines defined in a specified Azure DevOps project.

Instructions

List pipelines defined in a project.

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

Input Schema

NameRequiredDescriptionDefault
projectNoAzure DevOps project name or id. Defaults to AZDO_PROJECT if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral context, but it fails to mention important traits like pagination, sorting, permission requirements, or response details. The description only restates the tool's operation.

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 concise sentence with no wasted words. While it is minimal, it effectively communicates the core action without unnecessary detail.

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 listing tool with one optional parameter and no output schema, the description provides the essential purpose. However, it lacks details about response format, potential filters, or limitations, making it only marginally 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?

The single parameter 'project' already has a clear description in the input schema (name, default behavior), so the tool description adds no extra meaning. Schema coverage is 100%, meeting baseline expectations.

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 clearly states the verb 'List' and the resource 'pipelines defined in a project,' making its purpose straightforward. However, it does not explicitly differentiate from sibling tools like list_builds or list_projects, which are similarly named.

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?

The description provides no guidance on when to use this tool versus alternatives such as list_builds or list_projects, nor does it specify prerequisites 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