gitlab-mcp

Create Project Snippet

gitlab_create_project_snippet

Create a GitLab project snippet with 1 to 10 files, optional description, and configurable visibility settings.

Instructions

Create a project snippet with 1 to 10 files. visibility defaults to the project setting; public snippets are visible to anyone who can see the 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": {
      "title": "<title>",
      "files": "<files>"
    },
    "name": "gitlab_create_project_snippet"
  }
}

Input Schema

Name	Required	Description	Default
`files`	Yes
`title`	Yes
`project_id`	No
`visibility`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds genuine value by explaining the visibility default (inherits project setting) and what 'public' means in visibility terms, but it says nothing about permission requirements or the fact that repeated calls create duplicate snippets despite the non-idempotent hint.

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?

Two tight sentences with no filler, and the file-count constraint is front-loaded. Minor inefficiency: the visibility clause is useful but the sentence structure mixes default behavior with a definition of 'public'.

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 create tool with no output schema and annotations covering the safety profile, the definition gives enough to call it correctly at a basic level. It falls short on permission prerequisites and on what project_id being nullable means (personal vs project snippet).

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It only covers the files count bound (1-10, matching maxItems/minItems) and the visibility enum semantics; title, description, and especially project_id (which is nullable) are left unexplained, so it does not compensate for the coverage gap.

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?

States a specific verb and resource ("Create a project snippet") plus a hard constraint on payload size (1 to 10 files), which distinguishes it from the list/get/update/delete snippet siblings. It does not explicitly name those siblings, but the verb alone disambiguates it.

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 explicit when-to-use guidance, no prerequisites (required permissions, whether the project must allow snippets), and no pointer to gitlab_update_project_snippet for modifying an existing snippet. Usage is only implied by the verb 'Create'.

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

Deploy Server