gitlab-api

Get commits

gitlab_get_commits

Read-onlyIdempotent

Retrieve commits from a GitLab project repository, optionally filtered by branch, path, author, or date range, and return commit details with pagination support.

Instructions

Get commits.

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

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

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_commits"
  }
}

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

D1.8/5.0

Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds only the shape of the return wrapper and the fact that a ParameterError may be raised, while saying nothing about pagination, filtering, defaults, or how the many optional filters interact.

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 text is short, but it is under-specified rather than concise: it spends four lines on generic Args/Returns/Raises boilerplate while conveying almost no tool-specific meaning. It is front-loaded with a tautology, not with useful information.

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?

For a 39-parameter read tool with no schema descriptions and no output schema, the description is nowhere near complete. An agent cannot determine what most parameters do, how results are paginated, or what the parameters unrelated to commits (line, note, coverage, report_type, actions) are for.

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?

The schema has 39 parameters at 0% description coverage, and the description mentions none of them. Only a generic **kwargs placeholder is documented, leaving parameters like ref, since/until, path, with_stats, and author_email completely unexplained. This is a severe gap because the description does nothing to compensate for the schema's missing descriptions.

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

Purpose2/5

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

The description says only "Get commits," which restates the tool name and title without adding scope, such as whether it lists commits for a project, ref, or path. It gives no way to distinguish this tool from siblings like gitlab_get_commit (singular) or gitlab_get_commit_diff, so the agent cannot tell which one to pick.

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?

There is no when-to-use guidance, no prerequisite information, and no named alternatives. The agent must infer everything about when this tool is appropriate from the name alone.

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

Deploy Server