Skip to main content
Glama
Sign In
mcp-gitlab-crunchtools

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Release Tool

create_release_tool

Create a GitLab project release from a tag, including release notes, title, and target branch or commit, so versioned changes are published with accurate metadata.

Instructions

Create a new release for a GitLab project.

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": {
      "project_id": "<project_id>",
      "tag_name": "<tag_name>"
    },
    "name": "create_release_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoCommit SHA or branch to tag from (required if tag doesn't exist)
nameNoRelease title (defaults to tag_name)
tag_nameYesTag name for the release (created if it doesn't exist)
project_idYesProject ID or path
descriptionNoRelease notes (Markdown)
released_atNoRelease date (ISO 8601, default: now)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It omits that a tag will be created if it doesn't exist, that required permissions may be needed, that release creation is a state-changing write, and what happens on tag-name collision.

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

Conciseness4/5

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

A single efficient sentence with the key verb and resource front-loaded and zero filler. It is not padded, though the brevity veers toward under-specification rather than tightness.

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?

An output schema exists so return values need no explanation, but for a mutation tool with six parameters and no annotations the description is far too thin. It should at minimum convey the tag-creation side effect, required permissions, and the write nature of the call.

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%, with each of the six parameters documented including defaults and the ref/tag interaction, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what is already structured, which is the baseline case for a 3.

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?

The description states a specific verb and resource ('Create a new release') scoped to a GitLab project, so an agent immediately understands the operation. It stops short of distinguishing itself from siblings like list_releases_tool or get_release_tool, but the create verb does the differentiation implicitly.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the name alone that this is a write operation on releases rather than a read or update.

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