Skip to main content
Glama

gitlab_update_slack_integration

Configure Slack integration settings for GitLab projects by specifying the project ID, webhook URL, and optional channel and username. Streamline notifications and updates directly in Slack.

Instructions

Update Slack integration settings for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoThe Slack channel name
project_idYesThe ID or URL-encoded path of the project
usernameNoThe Slack username
webhookYesThe Slack webhook URL

Implementation Reference

  • The primary handler function that implements the logic for gitlab_update_slack_integration. It extracts parameters, validates required fields (project_id, webhook), and delegates to context.integrationsManager.updateSlackIntegration to perform the update.
    export const updateSlackIntegration: ToolHandler = async (params, context) => {
      const { project_id, webhook, username, channel, notify_only_broken_pipelines, notify_only_default_branch, ...options } = params.arguments || {};
      if (!project_id || !webhook) {
        throw new McpError(ErrorCode.InvalidParams, 'project_id and webhook are required');
      }
      
      const data = await context.integrationsManager.updateSlackIntegration(project_id as string | number, {
        webhook,
        username,
        channel,
        notify_only_broken_pipelines,
        notify_only_default_branch,
        ...options
      });
      return formatResponse(data);
    };
  • Defines the input schema and description for the gitlab_update_slack_integration tool, matching the handler parameters.
    name: 'gitlab_update_slack_integration',
    description: 'Update Slack integration settings for a project',
    inputSchema: {
      type: 'object',
      properties: {
        project_id: {
          type: 'string',
          description: 'The ID or URL-encoded path of the project'
        },
        webhook: {
          type: 'string',
          description: 'The Slack webhook URL'
        },
        username: {
          type: 'string',
          description: 'The Slack username'
        },
        channel: {
          type: 'string',
          description: 'The Slack channel name'
        }
      },
      required: ['project_id', 'webhook']
    }
  • Registers the tool name 'gitlab_update_slack_integration' to the updateSlackIntegration handler function from integration-handlers.ts in the central toolRegistry.
    gitlab_update_slack_integration: integrationHandlers.updateSlackIntegration,
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 'Update' which implies mutation, but doesn't mention permissions required, whether changes are reversible, rate limits, or what happens to existing settings not specified. This is inadequate for a mutation tool with zero annotation coverage.

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 zero wasted words. It's appropriately sized and front-loaded with the essential information, making it easy for an agent to parse quickly.

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 'update' entails (e.g., partial vs. full updates), what happens to unspecified fields, or what the response looks like. Given the complexity and lack of structured data, more behavioral 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?

Schema description coverage is 100%, so the schema already documents all 4 parameters. The description doesn't add any parameter-specific information 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 action ('Update') and target ('Slack integration settings for a project'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'gitlab_update_webhook' or 'gitlab_disable_slack_integration', which would be needed for a score of 5.

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 'gitlab_disable_slack_integration' or 'gitlab_add_webhook'. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction.

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