Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by mcpland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Protect Tag

gitlab_protect_tag

Protect a GitLab tag name or wildcard so only permitted roles can create it and protected CI/CD variables are available to its pipelines.

Instructions

Protect a tag name or wildcard (for example v*) so only allowed roles can create it and protected CI/CD variables reach its pipelines. create_access_level: 0 no one, 30 Developer, 40 Maintainer (default), 60 Admin.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "gitlab_protect_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
project_idNo
allowed_to_createNo
create_access_levelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent operation. The description adds meaningful behavioral context by explaining that protection limits who can create the tag and affects protected CI/CD variable availability, plus the default access level.

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 two dense sentences with the core purpose front-loaded and an efficient value legend for create_access_level. There is no unnecessary wording.

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?

The description covers the main effect and the access-level values, which is important for this mutation tool with no output schema. Still, for a four-parameter tool with no schema descriptions, it should explain allowed_to_create and project_id, and ideally state how existing protection rules are affected.

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?

With 0% schema description coverage, the description carries the full parameter burden. It does well on create_access_level by decoding 0, 30, 40, and 60, and it explains the wildcard meaning of name, but it leaves project_id and the allowed_to_create array structure unexplained.

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 names a specific verb and resource: protecting a tag name or wildcard. It also explains the concrete effect on tag creation permissions and CI/CD variables, making it distinguishable from creation, deletion, or unprotection siblings.

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?

Usage is implied by the stated effect: use it when tag creation should be restricted to certain roles or when protected CI/CD variables must reach tag pipelines. However, it does not explicitly name alternatives such as gitlab_unprotect_tag or gitlab_get_protected_tag, nor does it state when not to use this tool.

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