Bitbucket MCP Server

get_commit_diff

Retrieve the unified diff for any commit to review all code changes. Shows added, removed, and modified lines in standard patch format.

Instructions

Get the diff/patch of a specific commit showing all changes made. Returns unified diff format.

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>",
      "commit_id": "<commit_id>"
    },
    "name": "get_commit_diff"
  }
}

Input Schema

Name	Required	Description
`commit_id`	Yes	The commit hash (SHA).
`repo_slug`	Yes	The repository slug.
`workspace`	No	The workspace slug. Optional if BITBUCKET_WORKSPACE env var is set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 2, 2026

TDQS

A3.8/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 the return format (unified diff) and that all changes are shown, which is useful. However, it does not mention authentication requirements, rate limits, potential for large payloads, or any side effects, which would help fully set expectations.

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 two short sentences with no filler. The key purpose is first, and the output format is second. Every word earns its place.

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 relatively simple read-only tool with a fully documented schema, the description provides the essential purpose and output format. It could be improved by explicitly noting that this complements get_commit (which likely returns metadata) or mentioning any output size limitations, but these are minor given the strong context signals.

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 baseline is 3. The description adds no additional meaning for the parameters beyond what the schema already provides; it only states the tool's overall intention.

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?

The description uses a specific verb ('Get'), a specific resource ('the diff/patch of a specific commit'), and states the output format ('unified diff'). It clearly distinguishes this tool from sibling tools like get_commit by specifying the diff/patch content rather than commit metadata.

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?

The description implies the tool should be used when a commit's diff is needed, but it does not explicitly state when to use it versus alternatives such as get_commit or list_commits. There are no exclusions or comparisons with sibling tools, leaving the routing decision to inference.

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

Deploy Server