Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

List branches

bb_list_branches

Lists repository branches and flags the default branch, with an optional branch-name filter for targeted results.

Instructions

List branches of a repository with default-branch detection (isDefault flag). Optional branch name filter (server-side on Server/DC, client-side on Cloud).

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": "bb_list_branches"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number (Cloud only; from nextPageStart of the previous call). Ignored on Server/DC.
limitNoPage size (1-1000).
startNoZero-based page offset (Server/DC).
filterNoBranch name filter, e.g. 'feature/'.
projectKeyYesProject key (on Cloud: workspace slug).
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/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. It does disclose genuinely useful behavior beyond structured fields: the isDefault flag semantics and the fact that filtering is server-side on Server/DC but client-side on Cloud, which warns of potentially incomplete results on Cloud. It omits ordering, pagination behavior, and permission requirements, leaving meaningful gaps for a read tool with six parameters.

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?

Two tight sentences with the core purpose front-loaded and the deployment caveat immediately after. No filler, no restatement of the title or the parameter names.

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 six-parameter list tool with no output schema, the description covers purpose, the returned isDefault signal, and filter semantics, which is most of what an agent needs to call it correctly. It stops short of describing the branch record shape or pagination interplay between page/start/limit, which the schema documents but the description does not synthesize.

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

Parameters4/5

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

Schema description coverage is already 100%, so the baseline is 3, but the description adds real meaning: it explains that the 'filter' parameter is evaluated server-side on Server/DC and client-side on Cloud, a behavioral distinction the schema does not carry. That is a genuine semantic addition rather than a restatement.

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?

Names a specific verb and resource ('List branches of a repository') and adds a distinguishing capability (default-branch detection via isDefault). It is clearly separable from the mutating siblings bb_create_branch and bb_delete_branch based on the verb alone, though no sibling is named 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?

Usage is implied rather than stated: an agent can infer this is the read path for branch data, and the description hints that the filter parameter narrows results. However, it never says when to prefer this over alternatives, nor any prerequisites such as required read permissions on the repository.

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