gitlab-api

Get commit references

gitlab_get_commit_references

Read-onlyIdempotent

Fetch branches, tags, and other refs that point to a GitLab commit to trace where the commit is used across a repository.

Instructions

Get references of a commit.

Args: **kwargs: Additional parameters for the request.

Returns: Response: A wrapper containing the original response and a list of reference dictionaries.

Raises: 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_commit_references"
  }
}

Input Schema

Name	Required	Description	Default
`all`	No
`ref`	No
`data`	No
`line`	No
`name`	No
`note`	No
`page`	No
`path`	No
`force`	No
`since`	No
`state`	No
`stats`	No
`until`	No
`branch`	No
`actions`	No
`context`	No
`dry_run`	No
`message`	No
`coverage`	No
`per_page`	No
`ref_name`	No
`user_ids`	No
`group_ids`	No
`line_type`	No
`max_pages`	No
`rule_type`	No
`start_sha`	No
`project_id`	No
`target_url`	No
`with_stats`	No
`author_name`	No
`commit_hash`	No
`description`	No
`pipeline_id`	No
`report_type`	No
`author_email`	No
`start_branch`	No
`start_project`	No
`protected_branch_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedInput schema / properties / author_email / anyOf

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

addedInput schema / properties / author_email / title
```
Added value: +"Author Email"
```
changedInput schema / properties / page / default
```
Previous value: -1New value: +null
```
changedInput schema / properties / per_page / default
```
Previous value: -100New value: +null
```
addedInput schema / properties / project_id / default
```
Added value: +null
```

removedInput schema / properties / target_url / anyOf

Removed value: -[
-  {
-    "format": "uri",
-    "maxLength": 2083,
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / target_url / title
```
Added value: +"Target Url"
```
removedInput schema / required
```
Removed value: -[
-  "project_id"
-]
```

First observedv27.3.13Oct 25, 2026

TDQS

C2.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real value by saying the return is a wrapper containing the original response plus a list of reference dictionaries, and that invalid parameters raise ParameterError — but it says nothing about auth scope, pagination, or what kinds of references come back.

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

Conciseness2/5

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

The single purpose sentence is front-loaded and fine, but the rest is auto-generated docstring boilerplate (Args/Returns/Raises) whose Args section is vacuous and whose "**kwargs" claim conflicts with the closed schema. Noise outweighs signal for a 39-parameter tool.

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

Completeness1/5

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

A 39-parameter tool with no required parameters, zero schema coverage, and no output schema needs the description to explain which parameters matter and how to scope the lookup. It supplies none of that, leaving an agent unable to call this correctly without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

39 parameters at 0% schema description coverage, and the description names none of them — not commit_hash, project_id, ref, or any of the filter/pagination fields. The only parameter text is a kwargs catch-all, which is actively misleading since the schema sets additionalProperties=false. The description must compensate here and does not at all.

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

Purpose3/5

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

States a verb and resource ("Get references of a commit"), which is enough to know it retrieves commit-related references. But "references" is left undefined — could be branches, tags, issues, or merge requests — and nothing distinguishes it from siblings like gitlab_get_commit_merge_requests or gitlab_get_commit_statuses.

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 when-to-use guidance, no exclusions, and no mention of the sibling tools that fetch adjacent commit data. The only usage-ish text is the generic "**kwargs: Additional parameters for the request," which gives the agent nothing to decide with.

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

Deploy Server