Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_commit_statuses

Read-only

List commit statuses in a GitLab project, using filters for ref, stage, name, or pipeline ID to monitor CI/CD build outcomes.

Instructions

List statuses for a commit. Use this for a collection of resources; choose the corresponding get tool when you already know the single resource to inspect. It is read-only and does not mutate GitLab data; missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors. When project_id or group_id is accepted, provide the numeric ID or complete URL-encoded path described by the schema; use required identifiers and pagination fields exactly as documented.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoReturn all statuses, not only latest ones
refNoFilter statuses by Git ref
shaYesThe commit hash or name of a repository branch or tag
nameNoFilter statuses by status name or context
pageNoPage number for pagination (default: 1)
sortNoSort direction
stageNoFilter statuses by build stage
jmespathNoOptional JMESPath expression filtering the JSON result before return.
order_byNoField to order statuses by
per_pageNoNumber of items per page (max: 100, default: 20)
project_idYesProject ID or complete URL-encoded path to project
pipeline_idNoFilter statuses by pipeline ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.1.62
    • changedInput schema / required
      Previous value: -[
-  "sha",
-  "project_id"
-]New value: +[
+  "project_id",
+  "sha"
+]
  3. Addedv2.1.45
  4. Removedv2.1.43
  5. Addedv2.1.18
  6. Removedv2.1.14
  7. Addedv2.1.11
  8. Removedv2.1.10
  9. Addedv2.1.9

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds that the tool does not mutate GitLab data and describes error behavior for missing resources, invalid identifiers, insufficient permission, and rate limits. This is useful operational context beyond 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.

Conciseness4/5

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

Three compact sentences, with the core purpose first and operational notes after. Some boilerplate is present, such as the generic 'collection of resources' phrasing, but it is not excessive.

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

Completeness4/5

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

The tool has 12 parameters and no output schema, but every parameter is documented and the description covers read-only behavior, error conditions, and pagination. Missing details like default latest-only status are already implied by the schema's `all` parameter.

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%, so the schema already handles parameter meaning; the description mostly repeats project_id and pagination guidance. The mention of group_id is not present in this schema and adds slight noise rather than new semantic value.

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 action and resource: 'List statuses for a commit,' and contrasts it with a get-tool pattern for single resources. This clearly distinguishes it from siblings like list_commits or create_commit_status.

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

Usage Guidelines4/5

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

Explicitly says to use this tool when retrieving a collection and to choose the corresponding get tool when a single resource is known, providing a when/when-not rule. It does not name the exact get sibling, so the guidance is slightly generic.

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

Deploy Server

Other Tools