Skip to main content
Glama

gitlab_list_releases

Retrieve project releases with descriptions, assets, and release notes to find versions and access release information.

Instructions

List project releases Returns: GitLab releases (not just tags) Use when: Finding versions, release notes Includes: Assets, release notes, links

Different from tags:

  • Releases have descriptions, assets

  • Tags are just git references

Related tools:

  • gitlab_list_tags: Simple tag list

  • gitlab_create_release: Create release

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject identifier (auto-detected if not provided) Type: integer OR string Format: numeric ID or 'namespace/project' Optional: Yes - auto-detects from current git repository Examples: - 12345 (numeric ID) - 'gitlab-org/gitlab' (namespace/project path) - 'my-group/my-subgroup/my-project' (nested groups) Note: If in a git repo with GitLab remote, this can be omitted
order_byNoField to sort by Type: string (enum) Options vary by endpoint: - Commits: 'created_at', 'title' - Issues: 'created_at', 'updated_at', 'priority', 'due_date' - MRs: 'created_at', 'updated_at', 'title' Default: Usually 'created_at' Example: 'updated_at' to see recently modified items firstreleased_at
sortNoSort direction Type: string (enum) Options: 'asc' | 'desc' Default: Varies by context (usually 'desc' for time-based) Examples: - 'asc': A→Z, oldest→newest, smallest→largest - 'desc': Z→A, newest→oldest, largest→smallestdesc
per_pageNoNumber of results per page Type: integer Range: 1-100 Default: 20 Example: 50 (for faster browsing) Tip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing
pageNoPage number for pagination Type: integer Range: ≥1 Default: 1 Example: 3 (to get the third page of results) Note: Use with per_page to navigate large result sets

Implementation Reference

  • Handler function that implements the core logic for the gitlab_list_releases tool. Extracts parameters, detects project if needed, and calls the GitLabClient to fetch releases.
    def handle_list_releases(client: GitLabClient, arguments: Optional[Dict[str, Any]]) -> Dict[str, Any]:
        """Handle listing project releases"""
        project_id = require_project_id(client, arguments)
        order_by = get_argument(arguments, "order_by", "released_at")
        sort = get_argument(arguments, "sort", "desc")
        per_page = get_argument(arguments, "per_page", DEFAULT_PAGE_SIZE)
        page = get_argument(arguments, "page", 1)
        
        return client.list_releases(project_id, order_by, sort, per_page, page)
  • Registration of the handler function in the TOOL_HANDLERS dictionary, mapping the tool name to its handler.
    TOOL_LIST_TAGS: handle_get_tags,
    TOOL_LIST_RELEASES: handle_list_releases,
  • Tool schema definition and registration in the TOOLS list, including input schema validation for parameters like project_id, order_by, sort, pagination.
    types.Tool(
        name=TOOL_LIST_RELEASES,
        description=desc.DESC_LIST_RELEASES,
        inputSchema={
            "type": "object",
            "properties": {
                "project_id": {"type": "string", "description": desc.DESC_PROJECT_ID},
                "order_by": {"type": "string", "description": desc.DESC_ORDER_BY, "enum": ["released_at", "created_at"], "default": "released_at"},
                "sort": {"type": "string", "description": desc.DESC_SORT_ORDER, "enum": ["asc", "desc"], "default": "desc"},
                "per_page": {"type": "integer", "description": desc.DESC_PER_PAGE, "default": DEFAULT_PAGE_SIZE, "minimum": 1, "maximum": MAX_PAGE_SIZE},
                "page": {"type": "integer", "description": desc.DESC_PAGE_NUMBER, "default": 1, "minimum": 1}
            }
        }
    ),
  • Constant definition for the tool name used across the codebase for consistency.
    TOOL_LIST_RELEASES = "gitlab_list_releases"
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by specifying what's included in returns ('Assets, release notes, links') and clarifying the difference from tags. However, it doesn't mention pagination behavior, rate limits, authentication requirements, or error conditions that would be helpful for a list operation.

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

Conciseness5/5

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

The description is efficiently structured with clear sections: purpose statement, returns clarification, usage context, what's included, differentiation from tags, and related tools. Every sentence adds value with zero wasted words, making it easy for an agent to parse.

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

Completeness4/5

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

For a list operation with no annotations and no output schema, the description provides good context about what releases contain and how they differ from tags. However, it doesn't describe the return format structure or mention pagination behavior (though parameters suggest pagination exists), leaving some gaps for a tool that returns potentially large result sets.

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 the schema already fully documents all 5 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, which meets the baseline expectation when schema coverage is complete.

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

Purpose5/5

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

The description clearly states the verb ('List') and resource ('project releases'), specifying that it returns 'GitLab releases (not just tags)' which distinguishes it from the sibling tool gitlab_list_tags. The explicit distinction between releases and tags ('Releases have descriptions, assets; Tags are just git references') provides excellent differentiation.

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

Usage Guidelines5/5

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

The description includes explicit 'Use when' guidance ('Finding versions, release notes') and provides clear alternatives with 'Related tools' section that names gitlab_list_tags and gitlab_create_release. This gives the agent specific context about when to use this tool versus other options.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vijay-Duke/mcp-gitlab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server