Skip to main content
Glama
cuongdev

AWS CodePipeline MCP Server

by cuongdev

list_pipelines

Retrieve all AWS CodePipeline pipelines to monitor and manage continuous delivery workflows.

Instructions

List all CodePipeline pipelines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'list_pipelines' tool. It retrieves the list of pipelines from AWS CodePipeline via the CodePipelineManager and returns a formatted MCP-compatible response.
    export async function listPipelines(codePipelineManager: CodePipelineManager) {
      const codepipeline = codePipelineManager.getCodePipeline();
      const response = await codepipeline.listPipelines().promise();
      
      const pipelines = response.pipelines?.map((pipeline: AWS.CodePipeline.PipelineSummary) => ({
        name: pipeline.name || '',
        version: pipeline.version || 0,
        created: pipeline.created?.toISOString() || '',
        updated: pipeline.updated?.toISOString() || ''
      })) || [];
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ pipelines }, null, 2),
          },
        ],
      };
    }
  • The schema definition for the 'list_pipelines' tool, including name, description, and empty input schema since it takes no parameters.
    export const listPipelinesSchema = {
      name: "list_pipelines",
      description: "List all CodePipeline pipelines",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    } as const;
  • src/index.ts:136-138 (registration)
    Registration of the 'list_pipelines' tool handler in the MCP server's CallToolRequestSchema handler switch statement.
    case "list_pipelines": {
      return await listPipelines(codePipelineManager);
    }
  • src/index.ts:113-113 (registration)
    Inclusion of the 'list_pipelines' schema in the listTools response.
    listPipelinesSchema,
  • src/index.ts:9-12 (registration)
    Import of the listPipelines handler and listPipelinesSchema from the tools module.
    import { 
      listPipelines, 
      listPipelinesSchema 
    } from "./tools/list_pipelines.js";
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('List'), implying it's non-destructive, but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'all' entails (e.g., across regions/accounts). For a list tool with zero annotation coverage, this is inadequate.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place.

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 no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain what 'List all' returns (e.g., names, ARNs, summaries), how results are structured, or any limitations. For a tool in this context, more detail is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 CodePipeline pipelines'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'list_pipeline_executions' or 'get_pipeline_details', which would require more specificity about scope or output format.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_pipeline_details' (for specific pipelines) and 'list_pipeline_executions' (for executions rather than pipelines), the description lacks any context about use cases, prerequisites, or comparisons.

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/cuongdev/mcp-codepipeline-server'

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