Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Browse repository contents

bb_browse_repository

Browse a repository's default or specified branch to list root or directory entries and return truncated file content, so you can explore the tree before fetching files.

Instructions

Browse the default (or given) branch of a repository. Without 'path' lists the root directory; with a directory path lists entries; with a file path returns truncated content. Use this to explore the tree before fetching files.

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

Input Schema

NameRequiredDescriptionDefault
atNoBranch, tag or commit to browse (default: default branch).
pageNoOne-based page number (Cloud only; from nextPageStart of the previous call). Ignored on Server/DC.
pathNoPath inside the repository. Empty/omitted = root directory. Trailing slash selects a directory.
limitNoPage size (1-1000).
startNoZero-based page offset (Server/DC).
projectKeyYesProject key.
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/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 disclosure burden. It does valuable work by disclosing the three mode-dependent return shapes and that file content is truncated, but it says nothing about read-only/side-effect posture, permission or auth requirements, behavior on a nonexistent path, or pagination semantics that matter for a 7-param listing tool.

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?

Three short sentences, front-loaded with the resource and branching on the key argument, with zero filler. Each sentence changes what the agent would do next.

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 7-parameter tool with no output schema, the description usefully compensates by describing the returned shapes (entry listing versus truncated content). It is not fully complete on paging limits or failure behavior, but an agent can call it correctly from what is given.

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 every parameter is already documented, and the description's 'default (or given) branch' and root-vs-directory distinction largely restate the 'at' and 'path' schema text. Baseline 3 applies since the schema does the heavy lifting and the description adds no syntax or format detail beyond it.

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

Purpose5/5

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

States a specific verb and resource ('Browse ... a repository') and, unusually, distinguishes three distinct modes of operation by the 'path' argument: root listing, directory listing, and truncated file content. That lets an agent predict what it will get back and separates it from the sibling bb_get_file_content, which is alluded to via 'before fetching files'.

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

Usage Guidelines4/5

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

'Use this to explore the tree before fetching files' gives a clear usage context and implies the handoff to a file-fetching tool. It stops short of naming the alternative explicitly (bb_get_file_content) or saying when browsing should be skipped in favor of search_code, so it is strong context rather than a full routing rule.

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