Skip to main content
Glama

create_label

Create custom labels in GitLab projects to organize issues and merge requests with specific colors, descriptions, and priority levels.

Instructions

Create a new label in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID or URL-encoded path
nameYesThe name of the label
colorYesThe color of the label given in 6-digit hex notation with leading '#' sign
descriptionNoThe description of the label
priorityNoThe priority of the label

Implementation Reference

  • Zod schema defining input parameters for creating a GitLab project label: project_id (required), name (required), color (required hex string), description (optional), priority (optional number). Used for input validation of the 'create_label' MCP tool.
    export const CreateLabelSchema = z.object({
      project_id: z.coerce.string().describe("Project ID or URL-encoded path"),
      name: z.string().describe("The name of the label"),
      color: z
        .string()
        .describe("The color of the label given in 6-digit hex notation with leading '#' sign"),
      description: z.string().optional().describe("The description of the label"),
      priority: z.number().nullable().optional().describe("The priority of the label"),
    });
  • Zod schema for GitLab label response object, likely used for output validation of label-related tools including 'create_label'.
    export const GitLabLabelSchema = z.object({
      id: z.coerce.string(),
      name: z.string(),
      color: z.string(),
      text_color: z.string(),
      description: z.string().nullable(),
      description_html: z.string().nullable(),
      open_issues_count: z.number().optional(),
      closed_issues_count: z.number().optional(),
      open_merge_requests_count: z.number().optional(),
      subscribed: z.boolean().optional(),
      priority: z.number().nullable().optional(),
      is_project_label: z.boolean().optional(),
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Create' implies a write operation, it doesn't specify permissions required, whether the operation is idempotent, error conditions, or what happens on success/failure. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized and front-loaded, with zero wasted verbiage.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns the created label object), error handling, or dependencies. The context signals indicate this tool needs more behavioral context than provided.

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 schema fully documents all 5 parameters. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline score of 3 where the schema does the heavy lifting.

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 clearly states the action ('Create') and resource ('a new label in a project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_label' or 'list_labels' beyond the basic verb, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_label' or 'list_labels', nor does it mention prerequisites such as needing a valid project ID. It simply states what the tool does without contextual usage information.

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

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