bitbucket-mcp-server

list-branches

Retrieve and paginate branches for a Bitbucket repository by specifying its slug, with optional workspace and page controls to browse repository branch data.

Instructions

List branches for a repository

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": {
      "repo_slug": "<repo_slug>"
    },
    "name": "list-branches"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number or opaque next page URL returned by Bitbucket pagination
`pagelen`	No	Number of items per page (default: 10, min: 10, max: 100)
`repo_slug`	Yes	Repository slug/name
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries full behavioral burden but discloses nothing beyond a bare list operation. It does not mention that results are paginated (despite page/pagelen parameters), whether the read is unauthenticated or scope-limited, how many branches a typical repo returns, or what happens with private repos.

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?

A single front-loaded sentence with no filler or redundancy. It is lean to the point of under-specification, but the wording itself is efficient and unambiguous.

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 paginated listing tool with no output schema and no annotations, the description should at minimum mention paginated results and the repository scoping. It leaves the agent to infer return shape (branch names, commit hashes, default branch flag) and pagination semantics entirely from the schema.

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 page, pagelen, repo_slug, and the workspace env-var fallback are already documented in the schema. The description adds no syntax, default, or usage nuance for any of them, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List branches for a repository" states a verb and resource, but it is essentially the tool name expanded by two words, so it barely distinguishes itself beyond confirming a read of branches. Nothing identifies the provider (Bitbucket, visible only in the schema) or scope relative to siblings like repositories or commits.

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?

No when-to-use, when-not-to-use, or alternative is mentioned. An agent cannot tell from the description whether to prefer this over search or commits listing for exploring a repo, and prerequisites such as auth or workspace fallback are only hinted at in the schema.

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

Deploy Server