gitlab-api

Get latest release

gitlab_get_latest_release

Read-onlyIdempotent

Fetch current release details for a GitLab project using its project ID, including tag, description, and release date.

Instructions

Get information about the latest release in a project.

Args: **kwargs: Additional parameters for the request (e.g., project_id).

Returns: Response: A wrapper containing the original response and a Release model.

Raises: MissingParameterError: If the project_id is missing. 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_latest_release"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	No
`data`	No
`name`	No
`page`	No
`sort`	No
`simple`	No
`group_id`	No
`order_by`	No
`per_page`	No
`tag_name`	No
`max_pages`	No
`milestones`	No
`project_id`	No
`description`	No
`released_at`	No
`tag_message`	No
`total_pages`	No
`direct_asset_path`	No
`include_html_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

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

First observedv27.3.13Oct 25, 2026

TDQS

C2.8/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 the safety profile is covered. The description adds value beyond that by stating the response is a wrapper containing a Release model and by naming the error conditions (MissingParameterError, ParameterError). It does not disclose pagination behavior, though several supplied parameters (page, per_page, max_pages, total_pages) imply it does paginate.

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

Conciseness3/5

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

The docstring is short and front-loads the purpose sentence, but the Args block is pure boilerplate that occupies a third of the text while conveying almost nothing. The Raises section is useful; the '**kwargs' line is filler.

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?

For a 19-parameter tool with no output schema and zero schema descriptions, an agent cannot determine what most parameters do or how to target a specific project. The description does cover the return wrapper and failure modes, but the parameter surface—the dominant complexity here—is essentially undocumented.

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

Parameters2/5

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

Schema description coverage is 0% across 19 parameters, so the description must carry the burden and it does not. It collapses everything into '**kwargs: Additional parameters for the request (e.g., project_id)', leaving parameters like 'simple', 'include_html_description', 'milestones', and 'max_pages' completely unexplained.

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?

States a specific verb and resource ('Get information about the latest release in a project'), which is clearly distinct from a generic list tool. However, it never names or distinguishes itself from close siblings such as gitlab_get_releases, gitlab_get_release_by_tag, or gitlab_get_latest_release_evidence, so the agent must infer which one returns the latest release.

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 explicit when-to-use guidance and no mention of alternatives or exclusions, even though several sibling tools operate on releases. The only usage-relevant hint is the implied requirement of a project_id in the Raises section.

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

Deploy Server