gitlab-ci-mcp

Overview Schema Source Related Servers Discussions Admin

gitlab_get_pipeline

Read-onlyIdempotent

Retrieve a single GitLab pipeline with full timing details, including status, ref, source, queued/total durations, and timestamps, to diagnose slow or running pipelines.

Instructions

Get a single pipeline with full timing details.

Useful right after gitlab_list_pipelines — lists only return summaries. Returns status, ref, source, durations (queued/total), and started/finished timestamps.

Examples: - "Why was pipeline 123 slow" → check queued_duration and duration fields - "Is pipeline 456 still running" → look at status - Don't use to see individual jobs — use gitlab_get_pipeline_jobs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`pipeline_id`	Yes	Numeric pipeline ID (not ``iid``).
`project_path`	Yes	GitLab project path (e.g. 'my-org/my-repo'). Required by default. For legacy deployments only, set GITLAB_ALLOW_DEFAULT_PROJECT=true to use GITLAB_PROJECT_PATH when omitted.

Output Schema

Name	Required	Description	Default
`id`	Yes
`ref`	Yes
`source`	Yes
`status`	Yes
`web_url`	Yes
`duration`	Yes
`created_at`	Yes
`started_at`	Yes
`updated_at`	Yes
`finished_at`	Yes
`queued_duration`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.5Nov 5, 2026

removedInput schema / properties / project_path / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / project_path / default
```
Removed value: -null
```

changedInput schema / properties / project_path / description

Previous value: -"GitLab project path (e.g. 'my-org/my-repo'). When omitted, the default from GITLAB_PROJECT_PATH env var is used."New value: +"GitLab project path (e.g. 'my-org/my-repo'). Required by default. For legacy deployments only, set GITLAB_ALLOW_DEFAULT_PROJECT=true to use GITLAB_PROJECT_PATH when omitted."

addedInput schema / properties / project_path / minLength
```
Added value: +1
```
addedInput schema / properties / project_path / type
```
Added value: +"string"
```

changedInput schema / required

Previous value: -[
-  "pipeline_id"
-]New value: +[
+  "pipeline_id",
+  "project_path"
+]

First observedv0.5.1Apr 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavior the annotations cannot: it enumerates the payload (status, ref, source, queued/total durations, started/finished timestamps) and explains how to interpret the timing fields, which is real added context. It stops short of discussing pagination or failure modes, so it is not exhaustive.

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?

Purpose is front-loaded in one line, followed by routing context, return fields, and three short examples. Every element earns its place — the examples are not decorative, they teach the agent which field answers which question, and the negative routing sits at the end where it is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, yet the description still summarizes the key fields to guide interpretation. With 100% schema coverage, rich annotations, and only two required parameters, nothing an agent needs to call this correctly is missing.

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% and both parameters carry their own documentation, including the important "pipeline_id (not iid)" distinction, which lives in the schema rather than the description. The description adds no further meaning about parameter formats or edge cases, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get a single pipeline") plus the distinguishing scope: full timing details vs. the summaries returned by listing. It also names two siblings it differs from (gitlab_list_pipelines, gitlab_get_pipeline_jobs), so the agent can select it without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the trigger context ("right after gitlab_list_pipelines — lists only return summaries") and includes an explicit exclusion: "Don't use to see individual jobs — use gitlab_get_pipeline_jobs." Both when-to-use and when-not-to-use plus the named alternative are present.

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