Skip to main content
Glama

list_pipelines

Retrieve and filter pipelines for a GitLab project by status, branch, SHA, or username. Use parameters to narrow down results for CI/CD analysis.

Instructions

List pipelines for a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID or URL-encoded path
statusNoFilter by pipeline status
refNoFilter by branch or tag name
shaNoFilter by SHA
yaml_errorsNoFilter pipelines with YAML errors
usernameNoFilter by username who triggered
updated_afterNoReturn pipelines updated after date
updated_beforeNoReturn pipelines updated before date
order_byNoOrder by field
sortNoSort direction
pageNoPage number (1-indexed)
per_pageNoResults per page (1-100)
Behavior2/5

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

No annotations exist, so the description must carry the full burden. It merely says 'List pipelines' without disclosing read-only nature, pagination, or filtering behavior. The schema details these, but the description adds no behavioral context.

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?

A single, front-loaded sentence efficiently communicates the tool's purpose with no wasted words.

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 complexity (12 parameters, no output schema), the description is insufficient. It omits key details like pagination and return format, which the agent would need to use the tool correctly.

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% (12 parameters all described). The description adds no parameter meaning beyond the schema, meeting the baseline of 3 per rubric.

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?

The description clearly states 'List pipelines for a GitLab project', using a specific verb and resource. It distinguishes from sibling tools like 'get_pipeline' (individual) and 'list_pipeline_jobs' (different resource).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or context for when listing pipelines is appropriate.

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/yoda-digital/mcp-gitlab-server'

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