Skip to main content
Glama
jlromano

Bitbucket MCP Server

by jlromano

get_branch

Retrieve detailed information about a specific branch in a Bitbucket repository, including its commit history and metadata, to support repository management and development workflows.

Instructions

Get details of a specific branch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceYesThe workspace slug
repo_slugYesThe repository slug
branch_nameYesThe branch name

Implementation Reference

  • The actual implementation of the getBranch method, which makes the API call to fetch branch details.
    async getBranch(workspace: string, repoSlug: string, branchName: string): Promise<Branch> {
      const response = await this.api.get(`/repositories/${workspace}/${repoSlug}/refs/branches/${branchName}`);
      return response.data;
    }
  • The handler logic in index.ts that processes the 'get_branch' tool call by calling the BitbucketClient.
    case 'get_branch': {
      const { workspace, repo_slug, branch_name } = args as {
        workspace: string;
        repo_slug: string;
        branch_name: string;
      };
      const branch = await client.getBranch(workspace, repo_slug, branch_name);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(branch, null, 2),
          },
        ],
      };
  • src/index.ts:102-119 (registration)
    The registration of the 'get_branch' tool, including its schema and description.
    {
      name: 'get_branch',
      description: 'Get details of a specific branch',
      inputSchema: {
        type: 'object',
        properties: {
          workspace: {
            type: 'string',
            description: 'The workspace slug',
          },
          repo_slug: {
            type: 'string',
            description: 'The repository slug',
          },
          branch_name: {
            type: 'string',
            description: 'The branch name',
          },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get details'), implying non-destructive behavior, but lacks details on authentication needs, rate limits, error conditions, or return format. This is insufficient for a tool with no annotation coverage.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what details are returned, error handling, or how it differs from related tools. For a read operation with three required parameters, more context is needed to guide effective use.

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 the schema fully documents all three parameters. The description adds no additional meaning beyond implying the tool retrieves details for a branch, which aligns with the schema but doesn't provide extra context like parameter relationships or examples.

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?

The description clearly states the action ('Get details') and resource ('a specific branch'), making the purpose understandable. It doesn't distinguish from sibling tools like 'list_branches' or 'compare_branches', which would require explicit differentiation for a score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_branches' or 'get_commit', nor does it mention prerequisites or context for usage. It simply restates the basic function without operational context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jlromano/bitbucket-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server