Skip to main content
Glama

gitlab_get_merge_request_pipelines

Retrieve pipeline status and details for a GitLab merge request to monitor CI/CD progress and identify potential issues.

Instructions

Gets pipelines for a specific GitLab Merge Request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mrUrlYesThe URL of the GitLab Merge Request.

Implementation Reference

  • MCP tool handler that extracts mrUrl from arguments, calls the GitLabService.getMergeRequestPipelines method, and returns the JSON-stringified result.
    case 'gitlab_get_merge_request_pipelines': {
      if (!gitlabService) {
        throw new Error('GitLab service is not initialized.');
      }
      const { mrUrl } = args as { mrUrl: string };
      const result = await gitlabService.getMergeRequestPipelines(mrUrl);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including input schema requiring 'mrUrl' and description.
    {
      name: 'gitlab_get_merge_request_pipelines',
      description: 'Gets pipelines for a specific GitLab Merge Request.',
      inputSchema: {
        type: 'object',
        properties: {
          mrUrl: {
            type: 'string',
            description: 'The URL of the GitLab Merge Request.',
          },
        },
        required: ['mrUrl'],
      },
    },
  • src/index.ts:1182-1182 (registration)
    The tool is registered in the allTools array, which is filtered based on service availability and returned in ListToolsRequest.
    ];
  • GitLabService method that parses the MR URL to get projectPath and mrIid, then calls the GitLab API endpoint for merge request pipelines.
    async getMergeRequestPipelines(mrUrl: string): Promise<any[]> {
      const { projectPath, mrIid } = this.parseMrUrl(mrUrl, this.config.url);
      const encodedProjectPath = encodeURIComponent(projectPath);
      return this.callGitLabApi<any[]>(
        `projects/${encodedProjectPath}/merge_requests/${mrIid}/pipelines`,
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Gets') but does not describe the return format (e.g., list of pipelines with statuses), pagination behavior, error conditions, or authentication requirements. This leaves significant gaps for an agent to understand how to handle the tool's output and potential issues.

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, clear sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's purpose.

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 insufficient for a tool that retrieves data. It does not explain what the output contains (e.g., pipeline details, statuses, or IDs), how results are structured, or any behavioral nuances like rate limits or error handling. This leaves the agent with incomplete information to use the tool effectively.

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%, with the single parameter 'mrUrl' documented as 'The URL of the GitLab Merge Request.' The description does not add any additional meaning beyond this, such as URL format examples or validation rules. With high schema coverage, the baseline score of 3 is appropriate as the schema adequately covers parameter semantics.

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 ('Gets') and resource ('pipelines for a specific GitLab Merge Request'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'gitlab_get_pipeline_details' or 'gitlab_get_project_pipelines', which also retrieve pipeline-related data but for different scopes.

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 does not mention prerequisites, such as needing a valid merge request URL, or compare it to similar tools like 'gitlab_get_pipeline_details' for individual pipelines or 'gitlab_get_project_pipelines' for broader pipeline listings.

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/HainanZhao/mcp-gitlab-jira'

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