Skip to main content
Glama

gitlab_update_trigger_token

Modify a pipeline trigger token's description in a GitLab project by specifying the project ID and trigger ID. Essential for updating trigger details in CI/CD workflows.

Instructions

Update a pipeline trigger token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesThe new trigger description
project_idYesThe ID or URL-encoded path of the project
trigger_idYesThe ID of the trigger

Implementation Reference

  • The main handler function that executes the gitlab_update_trigger_token tool logic. It validates input parameters (project_id, trigger_id required; description optional) and delegates to the ciCdManager.updateTriggerToken method.
    export const updateTriggerToken: ToolHandler = async (params, context) => {
      const { project_id, trigger_id, description } = params.arguments || {};
      if (!project_id || !trigger_id) {
        throw new McpError(ErrorCode.InvalidParams, 'project_id and trigger_id are required');
      }
      
      const data = await context.ciCdManager.updateTriggerToken(project_id as string | number, trigger_id as number, description as string);
      return formatResponse(data);
    };
  • JSON schema defining the input parameters for the gitlab_update_trigger_token tool: project_id (string, required), trigger_id (number, required), description (string, required). Note: handler makes description optional.
    {
      name: 'gitlab_update_trigger_token',
      description: 'Update a pipeline trigger token',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'The ID or URL-encoded path of the project'
          },
          trigger_id: {
            type: 'number',
            description: 'The ID of the trigger'
          },
          description: {
            type: 'string',
            description: 'The new trigger description'
          }
        },
        required: ['project_id', 'trigger_id', 'description']
      }
  • Maps the tool name 'gitlab_update_trigger_token' to its handler function cicdHandlers.updateTriggerToken in the central tool registry.
    gitlab_update_trigger_token: cicdHandlers.updateTriggerToken,
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 for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't specify required permissions, whether changes are reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in 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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, side effects, or error handling, nor does it explain return values. For a 3-parameter update operation in a GitLab context, more context is needed for safe and effective use.

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 description coverage is 100%, so the schema already documents all three parameters (project_id, trigger_id, description) with clear descriptions. The tool description adds no additional meaning beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Update') and resource ('a pipeline trigger token'), making the purpose immediately understandable. It distinguishes from sibling tools like gitlab_create_trigger_token and gitlab_delete_trigger_token by specifying the update action. However, it doesn't explicitly mention what aspects are updated beyond what the parameters imply.

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 (e.g., needing an existing trigger token), compare with gitlab_create_trigger_token for creation, or specify scenarios where updating is appropriate versus deleting and recreating. The agent must infer usage from the tool name and parameters alone.

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

Related 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/rifqi96/mcp-gitlab'

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