Skip to main content
Glama
cuongdev

AWS CodePipeline MCP Server

by cuongdev

tag_pipeline_resource

Add or update tags for AWS CodePipeline resources to organize, track costs, and manage access control across pipeline components.

Instructions

Add or update tags for a pipeline resource

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pipelineNameYesName of the pipeline
tagsYesList of tags to add or update

Implementation Reference

  • The main handler function that executes the tool logic: retrieves pipeline ARN and applies tags using AWS CodePipeline SDK.
    export async function tagPipelineResource(
      codePipelineManager: CodePipelineManager, 
      input: {
        pipelineName: string;
        tags: Array<{ key: string; value: string }>;
      }
    ) {
      const { pipelineName, tags } = input;
      const codepipeline = codePipelineManager.getCodePipeline();
      
      // First, get the pipeline ARN
      const pipelineResponse = await codepipeline.getPipeline({ name: pipelineName }).promise();
      const resourceArn = pipelineResponse.metadata?.pipelineArn;
      
      if (!resourceArn) {
        throw new Error(`Could not find ARN for pipeline: ${pipelineName}`);
      }
      
      // Tag the resource
      await codepipeline.tagResource({
        resourceArn,
        tags: tags.map(tag => ({
          key: tag.key,
          value: tag.value
        }))
      }).promise();
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ 
              message: "Pipeline resource tagged successfully",
              resourceArn,
              tags
            }, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the tag_pipeline_resource tool, specifying pipelineName and tags array.
    export const tagPipelineResourceSchema = {
      name: "tag_pipeline_resource",
      description: "Add or update tags for a pipeline resource",
      inputSchema: {
        type: "object",
        properties: {
          pipelineName: { 
            type: "string",
            description: "Name of the pipeline"
          },
          tags: {
            type: "array",
            description: "List of tags to add or update",
            items: {
              type: "object",
              properties: {
                key: {
                  type: "string",
                  description: "Tag key"
                },
                value: {
                  type: "string",
                  description: "Tag value"
                }
              },
              required: ["key", "value"]
            }
          }
        },
        required: ["pipelineName", "tags"],
      },
    } as const;
  • src/index.ts:110-128 (registration)
    Registration of the tool schema in the list of available tools returned by ListToolsRequest handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          listPipelinesSchema,
          getPipelineStateSchema,
          listPipelineExecutionsSchema,
          approveActionSchema,
          retryStageSchema,
          triggerPipelineSchema,
          getPipelineExecutionLogsSchema,
          stopPipelineExecutionSchema,
          // Add new tool schemas
          getPipelineDetailsSchema,
          tagPipelineResourceSchema,
          createPipelineWebhookSchema,
          getPipelineMetricsSchema,
        ],
      };
    });
  • src/index.ts:195-200 (registration)
    Dispatch registration mapping tool name to handler function in the CallToolRequest handler switch statement.
    case "tag_pipeline_resource": {
      return await tagPipelineResource(codePipelineManager, input as {
        pipelineName: string;
        tags: Array<{ key: string; value: 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 mentions 'Add or update' which implies mutation, but doesn't specify permissions needed, whether tags are overwritten or merged, error conditions, or what happens on success. This leaves significant behavioral gaps for a mutation tool.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a simple tagging operation and front-loads the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after tagging (e.g., success response, error handling), nor does it provide context about tag limitations or system behavior. Given the complexity of modifying resources, more completeness 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 schema description coverage is 100%, with both parameters well-documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline score of 3 for adequate coverage without adding value.

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 action ('Add or update') and resource ('tags for a pipeline resource'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools that might also manipulate pipeline resources or tags, 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 like 'create_pipeline_webhook' or 'trigger_pipeline', nor does it mention prerequisites or constraints. It simply states what the tool does without contextual usage information.

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