Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Delete branch

bb_delete_branch

Deletes a branch from a Bitbucket project repository and refuses the operation with a structured DELETE_REFUSED error when the target is the default branch.

Instructions

Delete a branch. Refuses with a structured DELETE_REFUSED error when the target is the repository's default branch.

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_delete_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBranch to delete.
projectKeyYesProject key (on Cloud: workspace slug).
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 delivers one valuable detail: a structured DELETE_REFUSED error for default-branch targets. It omits irreversibility, required permissions, and response shape, which matter for a destructive operation.

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 short sentences with the action front-loaded and the failure condition second; nothing is wasted. Slightly terse given it is the only behavioral documentation available.

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 three-parameter destructive tool with no annotations and no output schema, the description covers the main guard but leaves permission requirements, reversibility, and return value unexplained. Adequate but with clear 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%, so projectKey, repositorySlug, and name are already documented, and the description adds no syntax or format detail beyond that. Baseline 3 applies when the schema does the explanatory work.

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 ('Delete a branch'), so the operation is unambiguous. It does not explicitly contrast with siblings like bb_create_branch or bb_list_branches, but the delete verb alone distinguishes it well enough.

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?

Usage is only implied by the operation name; no explicit guidance on when to reach for this versus related branch tools. The default-branch refusal hints at a 'when not' condition, but no alternatives or prerequisites (e.g., permissions) are named.

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