Skip to main content
Glama
Sign In
Bitbucket MCP Server

Bitbucket MCP Server

by pdogra1299
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_branches

Read-only

List branches in a Bitbucket repository, optionally filtering by name and paginating results, to find recently modified branches first.

Instructions

List branches (most recently modified first on Server).

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": {
      "workspace": "<workspace>",
      "repository": "<repository>"
    },
    "name": "list_branches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25)
startNoPagination start (default 0)
filterNoName filter
workspaceYesProject key (e.g., PROJ)
repositoryYesRepository slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.0.1
    • changedInput schema / properties / filter / description
      Previous value: -"Filter branches by name pattern (optional)"New value: +"Name filter"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of branches to return (default: 25)"New value: +"Max results (default 25)"
    • changedInput schema / properties / repository / description
      Previous value: -"Repository slug (e.g., \"my-repo\")"New value: +"Repository slug"
    • changedInput schema / properties / start / description
      Previous value: -"Start index for pagination (default: 0)"New value: +"Pagination start (default 0)"
    • changedInput schema / properties / workspace / description
      Previous value: -"Bitbucket workspace/project key (e.g., \"PROJ\")"New value: +"Project key (e.g., PROJ)"
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral detail — results are sorted most-recently-modified-first on Server — but says nothing about pagination behavior, total counts, or whether ordering differs on Cloud.

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?

Single short sentence with the key ordering information front-loaded and no filler. The parenthetical "on Server" is slightly cryptic but does not waste space.

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?

With five parameters, two required, and no output schema, the definition is minimally sufficient — the schema carries the parameters and the annotation carries safety. It still leaves gaps on pagination semantics and what a branch entry looks like, and the Server-only ordering caveat is not fully explained.

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 limit, start, filter, workspace, and repository are all documented in the schema. The description adds no parameter-level meaning beyond that, which is acceptable at this coverage level.

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 clear verb and resource ("list branches"), which is unambiguous. It does not distinguish itself from neighboring tools such as get_branch or list_branch_commits, so an agent must infer the boundary from the schemas.

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?

There is no guidance on when to use this versus get_branch (single branch) or list_branch_commits, and no mention of prerequisites or typical contexts. Usage is only implied by the tool name.

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

Deploy Server

Other Tools