Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_repository

Create a new GitLab project with name, visibility, description, and optional README. Place it in a group namespace or current user's namespace; get clear errors when permission or validation fails.

Instructions

Create a new GitLab project. Use this for a new resource or action; choose the corresponding update or edit tool when the resource already exists. It changes remote GitLab state and requires the necessary project or group permission; GitLab returns validation, conflict, permission, or rate-limit errors instead of silently applying an invalid request. When project_id or group_id is accepted, provide the numeric ID or complete URL-encoded path described by the schema; use required identifiers and pagination fields exactly as documented.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRepository name
jmespathNoOptional JMESPath expression filtering the JSON result before return.
visibilityNoRepository visibility level
descriptionNoRepository description
namespace_idNoGroup namespace ID to create the project in. Omit to use the current user's namespace.
initialize_with_readmeNoInitialize with README.md

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.1.62
    • addedInput schema / properties / namespace_id / maximum
      Added value: +9007199254740991
  3. Changed1 schema field changedv2.1.26
    • addedInput schema / properties / namespace_id
      Added value: +{
+  "description": "Group namespace ID to create the project in. Omit to use the current user's namespace.",
+  "minimum": 1,
+  "type": "integer"
+}
  4. Addedv2.1.18
  5. Removedv2.1.14
  6. Addedv2.1.11
  7. Removedv2.1.10
  8. Changed1 schema field changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  9. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the sparse openWorldHint annotation, the description discloses that the call changes remote GitLab state, requires project/group permission, and reports validation, conflict, permission, or rate-limit errors rather than silently succeeding. This is substantial behavioral context.

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?

The core purpose and usage are front-loaded and each sentence serves a distinct function. The final sentence is somewhat generic boilerplate, but the overall description remains compact.

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 moderate-complexity create tool with no output schema, the description covers lifecycle state, permissions, error behavior, and alternative-tool usage. The schema handles parameter details, though the description could have named update_project or clarified namespace_id instead of mentioning absent project_id/group_id.

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 baseline is 3. The description adds only generic advice about project_id/group_id and pagination fields, which are not present in this input schema, so it does not meaningfully enrich the parameter semantics.

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 opens with 'Create a new GitLab project', which names a specific verb, resource, and lifecycle stage. It also explicitly distinguishes this create action from update/edit tools, so it is unambiguous against siblings like update_project.

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

Usage Guidelines4/5

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

It says to use this for a new resource and to choose the corresponding update/edit tool when the resource already exists, providing an explicit when-not condition. It does not name update_project directly, but the alternative is clear from context.

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