Skip to main content
Glama

gitlab_get_integration

Retrieve details of a specific integration (e.g., Slack) for a GitLab project by providing the project ID and integration name. Simplify project management and configuration monitoring.

Instructions

Get integration details for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
integrationYesThe name of the integration (e.g., slack)
project_idYesThe ID or URL-encoded path of the project

Implementation Reference

  • The main handler function that implements the gitlab_get_integration tool logic, calling the integrationsManager and formatting the response.
     * Get integration handler
     */
    export const getIntegration: ToolHandler = async (params, context) => {
      const { project_id, integration_slug } = params.arguments || {};
      if (!project_id || !integration_slug) {
        throw new McpError(ErrorCode.InvalidParams, 'project_id and integration_slug are required');
      }
      
      const data = await context.integrationsManager.getIntegration(project_id as string | number, integration_slug as string);
      return formatResponse(data);
    };
  • The input schema definition for the gitlab_get_integration tool, specifying parameters project_id and integration.
    {
      name: 'gitlab_get_integration',
      description: 'Get integration details for a project',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'The ID or URL-encoded path of the project'
          },
          integration: {
            type: 'string',
            description: 'The name of the integration (e.g., slack)'
          }
        },
        required: ['project_id', 'integration']
      }
    },
  • The registration of gitlab_get_integration tool mapping to integrationHandlers.getIntegration in the tool registry.
    // Integration tools
    gitlab_list_integrations: integrationHandlers.listIntegrations,
    gitlab_get_integration: integrationHandlers.getIntegration,
    gitlab_update_slack_integration: integrationHandlers.updateSlackIntegration,
    gitlab_disable_slack_integration: integrationHandlers.disableSlackIntegration,
    gitlab_list_webhooks: integrationHandlers.listWebhooks,
    gitlab_get_webhook: integrationHandlers.getWebhook,
    gitlab_add_webhook: integrationHandlers.addWebhook,
    gitlab_update_webhook: integrationHandlers.updateWebhook,
    gitlab_delete_webhook: integrationHandlers.deleteWebhook,
    gitlab_test_webhook: integrationHandlers.testWebhook,
  • Import of integrationHandlers module containing the getIntegration function.
    import * as integrationHandlers from "../handlers/integration-handlers.js";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error conditions, or what the output looks like (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps.

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 retrieval tool 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'integration details' include, what format they're returned in, or any behavioral aspects like error handling. For a tool with no structured metadata, more context would be helpful.

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 input schema has 100% description coverage, clearly documenting both required parameters ('integration' and 'project_id'). The description doesn't add any parameter details beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

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 ('Get') and resource ('integration details for a project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'gitlab_list_integrations' or 'gitlab_get_webhook', which could cause confusion about when to use each.

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_list_integrations' (which likely lists all integrations) or 'gitlab_get_webhook' (which retrieves a specific webhook integration). There's no mention of prerequisites, context, or exclusions.

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