gitlab-api

Get pipeline

gitlab_get_pipeline

Read-onlyIdempotent

Retrieve details for a specific GitLab project pipeline using project_id and pipeline_id, so you can inspect pipeline status, ref, and related metadata.

Instructions

Get information about a specific pipeline in a project.

Args: **kwargs: Additional parameters for the request (e.g., project_id, pipeline_id).

Returns: Response: A wrapper containing the original response and a Pipeline model.

Raises: MissingParameterError: If the project_id or pipeline_id is missing. ParameterError: If invalid parameters are provided.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_get_pipeline"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	No
`data`	No
`page`	No
`status`	No
`per_page`	No
`max_pages`	No
`variables`	No
`project_id`	No
`pipeline_id`	No
`total_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

changedInput schema / properties / page / default
```
Previous value: -1New value: +null
```
changedInput schema / properties / per_page / default
```
Previous value: -100New value: +null
```

First observedv27.3.13Oct 25, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds useful context about the return wrapper and Pipeline model plus MissingParameterError and ParameterError conditions, but it does not mention authentication needs, rate limits, or pagination behavior despite pagination-related parameters in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is clear and front-loaded, and the Args/Returns/Raises structure is easy to scan. However, the Args section uses generic **kwargs language that does not earn its place and provides little concrete guidance.

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 10-parameter pipeline retrieval tool with no output schema and no schema parameter descriptions, the definition is incomplete. It covers purpose, return wrapper, and error behavior, but leaves most parameter semantics and pagination/filtering behavior unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 10 parameters with 0% description coverage, and the description only vaguely mentions project_id and pipeline_id as examples under **kwargs. It does not explain ref, status, variables, page, per_page, max_pages, total_pages, or data, and the **kwargs framing does not align well with the explicit input schema.

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 states a specific verb and resource: get information about a specific pipeline in a project. It is clear what the tool retrieves, but it does not explicitly distinguish itself from sibling tools such as gitlab_get_pipelines or gitlab_get_pipeline_jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'specific pipeline in a project,' suggesting it is for retrieving one known pipeline rather than listing pipelines. However, there is no explicit guidance on when to use this instead of gitlab_get_pipelines, gitlab_get_pipeline_jobs, or other pipeline-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server