gitlab-api

Get releases

gitlab_get_releases

Read-onlyIdempotent

Retrieve GitLab project release information, including tags, milestones, and release dates, with filtering and pagination options for targeted results.

Instructions

Get information about releases in a project.

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

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

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

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 non-destructive behavior, so the safety profile is covered. The description adds that a MissingParameterError is raised when project_id is absent and a ParameterError for invalid parameters, plus that the result is a wrapper containing the original response and a list of Release models. It does not disclose pagination behavior despite page/per_page/max_pages/total_pages parameters, leaving a meaningful gap.

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 one-line purpose is front-loaded and the Returns/Raises block carries real value. But the 'Args: **kwargs: Additional parameters for the request (e.g., project_id)' block is boilerplate filler that occupies space without explaining the 19 concrete parameters.

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 tool with 19 undocumented parameters, no output schema, and no parameter descriptions, the definition is substantially incomplete. The return-wrapper and error notes partially compensate, but an agent still cannot tell how to filter releases by tag, sort results, or interpret the pagination controls from this text.

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?

19 parameters with 0% schema description coverage means the description carries the full burden, yet it only mentions project_id and ignores ref, tag_name, name, sort, order_by, simple, include_html_description, and the rest. Several of those parameters look like create/update-release fields, and the description does nothing to clarify which apply to a read call or how filtering and sorting work.

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?

Names a specific verb and resource: 'Get information about releases in a project.' An agent can tell this is a release-listing read. However, it does not differentiate from close siblings like gitlab_get_group_releases, gitlab_get_latest_release, or gitlab_get_release_by_tag, so scope is clear but not disambiguated.

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 exclusions, and no reference to alternatives such as the group-level or by-tag release getters. The only contextual instruction is the implies-required project_id via the Raises section, which is a precondition rather than usage guidance.

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

Deploy Server