Skip to main content
Glama
jmrplens

Gitlab MCP Server

by jmrplens
OverviewSchemaRelated ServersScoreDiscussions
Go
Hybrid

Tag

gitlab_tag
Destructive

Manage Git tags in a project: create, list, delete, protect, unprotect, and verify GPG signatures.

Instructions

Use {"action":"create","params":{...}}; only top-level keys are action and params. Action params schema: gitlab://schema/meta/gitlab_tag/.

Manage Git tags and tag protections in a project, plus GPG signature inspection. Delete is destructive and also removes any release attached to the tag. When to use: create/list/delete tags, protect or unprotect tag patterns, verify a tag's GPG/X.509 signature. NOT for: releases (use gitlab_release — a release wraps a tag with notes/assets), branches (use gitlab_branch), repository file/commit operations (use gitlab_repository).

Returns:

  • list / list_protected: array of {name, target, message, protected, ...} with pagination.

  • get / create / get_protected / protect: tag or protection object.

  • get_signature: {signature_type, gpg_key_id, verification_status, ...} or X.509 equivalent.

  • delete / unprotect: {success: bool, message: string}. Errors: 404 not found, 403 forbidden (hint: requires Maintainer+ to protect/unprotect), 400 invalid params (hint: tag name must not exist for create).

Param conventions: * = required. All actions need project_id*. Access levels: 0 = no one, 30 = Developer, 40 = Maintainer.

  • create: project_id*, tag_name*, ref* (branch/tag/SHA), message (annotated tag if non-empty)

  • get / delete: project_id*, tag_name*

  • list: project_id*, search, order_by (name/updated/version), sort (asc/desc)

  • get_signature: project_id*, tag_name*

  • list_protected: project_id*

  • get_protected / unprotect: project_id*, tag_name*

  • protect: project_id*, tag_name* (literal or wildcard e.g. 'v*'), create_access_level (0/30/40), allowed_to_create (array of {user_id|group_id|deploy_key_id|access_level})

See also: gitlab_release (releases use tags as anchors), gitlab_repository (commits referenced by tags), gitlab_branch (branches).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform. Pick exactly one of the values in `enum`. Each action expects its own `params` object — see the tool description for the per-action parameter list.
paramsNoAction-specific parameters as a JSON object. Required and optional fields differ per action. This envelope schema stays broad; runtime validation applies the chosen action's schema after reserved meta keys like `confirm` are stripped. For the JSON Schema of a specific action's `params`, read the MCP resource `gitlab://schema/meta/{tool}/{action}` (replace placeholders with the tool name and the chosen action).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
next_stepsNoOptional. Suggested follow-up actions or tool calls for the LLM, contextual to the result.
paginationNoPresent on list actions. Use `has_more` and `next_page` to paginate through results.

Tool Definition Quality

A4.8/5.0
Behavior4/5

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

Annotations already indicate destructiveHint and openWorldHint. The description adds specific behavioral details: 'Delete is destructive and also removes any release attached to the tag.' It also mentions authorization requirements ('403 forbidden, hint: requires Maintainer+') and validation hints, going beyond what annotations provide. However, it does not fully enumerate all possible side effects implied by openWorldHint.

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 well-organized: starts with the action envelope format, then a high-level summary, usage guidance, return types, errors, parameter conventions, and detailed param lists. Every sentence serves a purpose, and the structure is front-loaded with the most critical information. Despite length, it remains clear and efficient.

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

Completeness5/5

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

Given the complexity (9 actions, variable parameters, output schema exists), this description covers all necessary aspects: purpose, usage scenarios, parameter details per action, return structures, error codes and hints, authorization requirements, and cross-references to sibling tools. It leaves no significant gaps for an AI agent to use the tool correctly.

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

Parameters5/5

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

Although the input schema has 100% description coverage for its two parameters (action and params), the description adds enormous value by detailing each action's required and optional parameters in a structured list. This per-action parameter breakdown is essential for correct tool invocation and significantly exceeds the schema's generic description.

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 'Manage Git tags and tag protections in a project, plus GPG signature inspection.' and lists specific actions (create/list/delete tags, protect/unprotect, verify signature). It explicitly distinguishes from sibling tools like gitlab_branch, gitlab_release, and gitlab_repository, making the purpose unmistakable.

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 explicitly says 'When to use: ... NOT for: ...' and names alternative tools for releases, branches, and repository operations. It also includes 'See also: gitlab_release, gitlab_repository, gitlab_branch' at the end, providing clear guidance on when to choose this tool over others.

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/jmrplens/gitlab-mcp-server'

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