Skip to main content
Glama
Sign In
gitlab mcp

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_commits

Read-only

List GitLab repository commits with filters for author, date range, file path, branch, and pagination to inspect project history.

Instructions

List repository commits with filtering options. For one known resource, use the matching get tool.

Input Schema

NameRequiredDescriptionDefault
allNoEvery commit in the repository
pageNoPage number (default 1)
pathNoFile path
orderNodefault or topo
sinceNoCommits on or after this ISO 8601 datetime
untilNoCommits on or before this ISO 8601 datetime
authorNoCommit author
summaryNoIf true, return only high-signal fields (id, iid, title, state, web_url, …). Default false keeps the full GitLab JSON.
jmespathNoOptional JMESPath expression filtering the JSON result before return.
per_pageNoItems per page (max 100, default 20)
ref_nameNoBranch, tag, or revision range. Default: default branch.
trailersNoInclude Git trailers
project_idYesProject ID or URL-encoded path
with_statsNoInclude per-commit stats
first_parentNoFollow only the first parent of merges

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.3.22
    • changedInput schema / properties / all / description
      Previous value: -"Retrieve every commit from the repository"New value: +"Every commit in the repository"
    • changedInput schema / properties / author / description
      Previous value: -"Search commits by commit author"New value: +"Commit author"
    • changedInput schema / properties / first_parent / description
      Previous value: -"Follow only the first parent commit upon seeing a merge commit"New value: +"Follow only the first parent of merges"
    • changedInput schema / properties / order / description
      Previous value: -"List commits in order"New value: +"default or topo"
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination (default: 1)"New value: +"Page number (default 1)"
    • changedInput schema / properties / path / description
      Previous value: -"The file path"New value: +"File path"
    • changedInput schema / properties / per_page / description
      Previous value: -"Number of items per page (max: 100, default: 20)"New value: +"Items per page (max 100, default 20)"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID or complete URL-encoded path to project"New value: +"Project ID or URL-encoded path"
    • changedInput schema / properties / ref_name / description
      Previous value: -"The name of a repository branch, tag or revision range, or if not given the default branch"New value: +"Branch, tag, or revision range. Default: default branch."
    • changedInput schema / properties / since / description
      Previous value: -"Only commits after or on this date are returned in ISO 8601 format YYYY-MM-DDTHH:MM:SSZ"New value: +"Commits on or after this ISO 8601 datetime"
    • changedInput schema / properties / trailers / description
      Previous value: -"Parse and include Git trailers for every commit"New value: +"Include Git trailers"
    • changedInput schema / properties / until / description
      Previous value: -"Only commits before or on this date are returned in ISO 8601 format YYYY-MM-DDTHH:MM:SSZ"New value: +"Commits on or before this ISO 8601 datetime"
    • changedInput schema / properties / with_stats / description
      Previous value: -"Stats about each commit are added to the response"New value: +"Include per-commit stats"
  2. Changed1 schema field changedv2.3.8
    • addedInput schema / properties / summary
      Added value: +{
+  "description": "If true, return only high-signal fields (id, iid, title, state, web_url, …). Default false keeps the full GitLab JSON.",
+  "type": "boolean"
+}
  3. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  4. Addedv2.1.45
  5. Removedv2.1.43
  6. Addedv2.1.18
  7. Removedv2.1.14
  8. Addedv2.1.11
  9. Removedv2.1.10
  10. Changed2 schema fields changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / required
      Added value: +[
+  "project_id"
+]
  11. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already supply readOnlyHint and openWorldHint, so the description's main job is to add the operational detail they don't cover. It says nothing about pagination defaults, full-vs-summary payload behavior, ordering semantics, or result size limits, so an agent learns nothing about runtime behavior it could not already infer from the structured fields.

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?

Two short sentences, front-loaded with the verb and resource, no filler adjectives or restated titles. The second sentence is slightly boilerplate and vague, which keeps it out of the top band.

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

Completeness3/5

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

With 15 parameters and no output schema, the description is thin, but the schema is fully described and the annotations cover the safety profile, so the essential calling information is present. What is missing is guidance on the interaction of paging, summary/jmespath shaping, and traversal flags (all, first_parent) that matter for a commit listing tool.

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 every one of the 15 parameters is already documented in the schema, including the nuanced summary, jmespath, and ref_name entries. The description's "filtering options" adds no meaning beyond that, making the baseline 3 correct.

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?

"List repository commits with filtering options" states a specific verb plus resource and implies the filterable axes. It also gestures at separation from the single-resource getter, though it never names get_commit, so the sibling differentiation is suggestive rather than explicit.

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

Usage Guidelines3/5

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

"For one known resource, use the matching get tool" gives a real when-not-to-use condition (single commit already identified), which is more than nothing. But "matching get tool" is unresolved phrasing among 37 siblings, and nothing says when to prefer filters like path/ref_name/since versus list_branches or search_repositories.

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