Skip to main content
Glama
stefanskiasan

Azure DevOps MCP Server for Cline

list_pipelines

Retrieve all Azure DevOps pipelines in a project. Filter results by folder path or pipeline name to find specific CI/CD workflows.

Instructions

List all pipelines in the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoFilter pipelines by folder path (optional)
nameNoFilter pipelines by name (optional)

Implementation Reference

  • The handler function that fetches and returns the list of pipelines from Azure DevOps using the Build API.
    export async function getPipelines(args: GetPipelinesArgs, config: AzureDevOpsConfig) {
      AzureDevOpsConnection.initialize(config);
      const connection = AzureDevOpsConnection.getInstance();
      const pipelineApi = await connection.getBuildApi();
    
      try {
        const pipelines = await pipelineApi.getDefinitions(
          config.project,
          args.name,
          args.folder
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(pipelines, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        if (error instanceof McpError) throw error;
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get pipelines: ${errorMessage}`
        );
      }
    }
  • Tool definition including name, description, and input schema for 'list_pipelines'.
    {
      name: 'list_pipelines',
      description: 'List all pipelines in the project',
      inputSchema: {
        type: 'object',
        properties: {
          folder: {
            type: 'string',
            description: 'Filter pipelines by folder path (optional)',
          },
          name: {
            type: 'string',
            description: 'Filter pipelines by name (optional)',
          },
        },
      },
    },
  • src/index.ts:158-162 (registration)
    Dispatches the 'list_pipelines' tool call to the appropriate handler function.
    case 'list_pipelines':
      result = await tools.pipeline.getPipelines(
        validateArgs(request.params.arguments, 'Pipeline arguments required')
      );
      break;
  • Registers the tool definitions and initializes the handler functions for pipeline tools.
    export const pipelineTools = {
      initialize: (config: AzureDevOpsConfig) => ({
        getPipelines: (args: any) => getPipelines(args, config),
        triggerPipeline: (args: any) => triggerPipeline(args, config),
        definitions,
      }),
      definitions,
  • Type definition for the input arguments of the getPipelines handler.
    interface GetPipelinesArgs {
      folder?: string;
      name?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't address permissions, pagination, rate limits, or response format. For a tool with zero annotation coverage, this is insufficient transparency.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple list tool, making it highly efficient.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'pipeline' entails in this context, how results are returned, or any behavioral constraints. For a tool with no structured metadata, more context is needed.

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 description mentions no parameters, but the input schema has 100% coverage with clear descriptions for both optional filters ('folder' and 'name'). Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description adds no parameter semantics beyond what the schema provides.

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 resource ('all pipelines in the project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'list_projects' or 'list_work_items' beyond the resource type, which prevents a perfect score.

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. It doesn't mention prerequisites, context for filtering, or how it relates to sibling tools like 'trigger_pipeline' or other list operations. This leaves the agent without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanskiasan/azure-devops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server