gitlab-api

Get pipelines

gitlab_get_pipelines

Read-onlyIdempotent

Retrieve pipeline information for a specific GitLab project by project ID, with optional filters for status, ref, and pagination.

Instructions

Get information about pipelines for a specific project.

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

Returns: Response: A wrapper containing the original response and a list of Pipeline models.

Raises: MissingParameterError: If the project_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_pipelines"
  }
}

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.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds a return wrapper and error conditions, but it omits pagination and filtering behavior despite several pagination-related params, and it uses generic '**kwargs' phrasing rather than describing actual request behavior.

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

Conciseness4/5

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

The description is short, front-loaded with the main purpose, and organized into Args/Returns/Raises sections. The Args section is boilerplate and unhelpful, but the overall text is not bloated.

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 listing tool with no output schema and no schema descriptions, the return and error notes help somewhat. However, essential filtering and pagination semantics are missing, making the definition incomplete for correct invocation.

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?

Schema description coverage is 0% across 10 parameters, so the description must compensate. It only mentions project_id in the error text and otherwise uses a generic '**kwargs' line, leaving ref, status, page, per_page, max_pages, variables, pipeline_id, and total_pages unexplained; it also implies project_id is required while the schema marks no required parameters.

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?

States a specific verb and resource: getting pipelines for a specific project. This distinguishes it from the singular gitlab_get_pipeline, though it does not explicitly name sibling alternatives.

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?

Provides a prerequisite by noting MissingParameterError when project_id is missing. However, it gives no guidance on when to use this tool instead of siblings like gitlab_get_pipeline or gitlab_get_pipeline_jobs, and no guidance on filtering by ref or status.

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

Deploy Server