Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Create branch

bb_create_branch

Create a Bitbucket branch from a specified branch, tag, or commit, defaulting to the repository's default branch when no start point is given.

Instructions

Create a branch in a repository, optionally from a specific start point (branch name, tag or commit). Refuses nothing server-side; default-branch protection applies only to deletion.

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": {
      "projectKey": "<projectKey>",
      "repositorySlug": "<repositorySlug>",
      "name": "<name>"
    },
    "name": "bb_create_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew branch name, e.g. 'feature/mcp-test'.
projectKeyYesProject key (on Cloud: workspace slug).
startPointNoBranch/tag/commit to start from (default: the repository's default branch).
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add one genuinely useful fact: creation is not blocked server-side and default-branch protection only applies to deletion. However, it omits critical write-path behavior such as what happens when the branch name already exists (error vs. idempotent success), whether the operation is audited, and what constitutes a failure.

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 sentences, front-loaded with the core action and no filler. The second clause about server-side refusal is slightly awkwardly phrased but earns its place by conveying real behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation tool with no annotations and no output schema, the description should say what is returned (branch object, ref, URL) and how duplicate names are handled. It covers the creation semantics adequately but leaves those caller-relevant gaps.

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%, and the description's parameter content (start point may be a branch, tag or commit; defaults exist) merely restates what the schema already documents for startPoint. It adds no format hints, constraints, or edge-case semantics beyond that, so the baseline 3 applies.

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 branch in a repository") and the optional start-point scope. It is clearly distinguishable from bb_delete_branch and bb_list_branches, though it does not name or contrast with them explicitly.

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

Usage Guidelines3/5

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

The description implies the use case (creating a branch, optionally from a start point) but gives no explicit when-to-use or when-not-to-use guidance, no prerequisites such as required permissions, and no pointer to alternatives like bb_list_branches for checking existing names.

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