Skip to main content
Glama

gitlab_create_branch

Create a new branch in a GitLab project by specifying the project path, branch name, and source reference for development or feature work.

Instructions

Creates a new branch in a GitLab project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesThe path of the GitLab project.
branchNameYesThe name of the new branch.
refYesThe branch or SHA to create the branch from.

Implementation Reference

  • MCP server request handler for the 'gitlab_create_branch' tool. Extracts arguments, calls GitLabService.createBranch, and returns success response.
    case 'gitlab_create_branch': {
      if (!gitlabService) {
        throw new Error('GitLab service is not initialized.');
      }
      const { projectPath, branchName, ref } = args as { projectPath: string; branchName: string; ref: string };
      const result = await gitlabService.createBranch(projectPath, branchName, ref);
      return {
        content: [
          {
            type: 'text',
            text: `Branch created successfully: ${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:770-790 (registration)
    Tool registration in allTools array, including name, description, and input schema.
      name: 'gitlab_create_branch',
      description: 'Creates a new branch in a GitLab project.',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description: 'The path of the GitLab project.',
          },
          branchName: {
            type: 'string',
            description: 'The name of the new branch.',
          },
          ref: {
            type: 'string',
            description: 'The branch or SHA to create the branch from.',
          },
        },
        required: ['projectPath', 'branchName', 'ref'],
      },
    },
  • GitLabService.createBranch method: core logic that makes the POST API call to GitLab to create the branch.
    async createBranch(projectPath: string, branchName: string, ref: string): Promise<any> {
      const encodedProjectPath = encodeURIComponent(projectPath);
      return this.callGitLabApi<any>(
        `projects/${encodedProjectPath}/repository/branches`,
        'POST',
        {
          branch: branchName,
          ref: ref,
        },
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('creates') but lacks critical details: whether this requires specific permissions, if it's idempotent (handling existing branches), rate limits, error conditions (e.g., invalid ref), or what happens on success (e.g., branch creation confirmation). For a mutation tool, this is a significant gap in transparency.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence earns its place by conveying essential information.

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 incomplete. It doesn't address behavioral aspects like permissions, idempotency, or error handling, nor does it hint at return values (e.g., success confirmation or branch details). Given the complexity of creating a branch in a version control system, more context is needed for effective agent use.

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?

The input schema has 100% description coverage, clearly documenting all three required parameters (projectPath, branchName, ref). The description adds no additional semantic context beyond what's in the schema, such as formatting examples or constraints (e.g., branch naming conventions). With high schema coverage, a baseline score of 3 is appropriate as 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 ('creates') and resource ('new branch in a GitLab project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'gitlab_delete_branch' or 'gitlab_list_branches' beyond the basic verb, missing an opportunity to clarify its unique role in the toolset.

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. It doesn't mention prerequisites (e.g., needing project access), compare it to similar tools like 'gitlab_list_branches' for checking existing branches, or specify use cases (e.g., feature development vs. hotfixes). This leaves the agent without context for tool selection.

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

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