Skip to main content
Glama

list_commit_statuses

Read-only

Retrieve and filter commit statuses by project ID and commit SHA. Supports filtering by ref, stage, name, pipeline ID, and pagination.

Instructions

List statuses for a commit

Input Schema

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds no further behavioral context (e.g., no mention of permissions, rate limits, or return format).

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 single-sentence description is front-loaded and concise, but could be slightly more informative without significant bloat.

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?

Despite rich schema and annotations, the description lacks context about typical use cases, pagination behavior, or the nature of commit statuses (e.g., CI/CD pipelines). This is a gap for a tool with 11 parameters.

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 input schema fully documents all 11 parameters. The description provides no additional meaning beyond the 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 clearly states 'List statuses for a commit,' using a specific verb and resource. It distinguishes from sibling tool 'create_commit_status' by indicating it's a read-only listing operation.

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 on when to use this tool vs alternatives such as 'get_commit' or 'create_commit_status.' No exclusions or context provided.

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/zereight/gitlab-mcp'

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