Bitbucket MCP

get_diff

Retrieve the unified diff for a pull request to review code changes. Provides a truncated diff up to 8 KB for quick inspection.

Instructions

Get the unified diff for a pull request (truncated to 8 KB)

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>",
      "pr_id": "<pr_id>"
    },
    "name": "get_diff"
  }
}

Input Schema

Name	Required	Description	Default
`pr_id`	Yes	Pull request ID
`repo_slug`	Yes	Repository slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-developmentSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly reveals the non-obvious truncation to 8 KB and identifies the output format as a unified diff. It does not comment on side effects, but 'Get' reasonably implies a read operation.

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?

A single, front-loaded sentence conveys the core action, the target resource, and the important truncation caveat without wasted words. Every element 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 simple two-parameter read tool, the description covers purpose, output type, and the main limitation. It lacks explicit mention of read-only guarantees or behavior when the diff exceeds the truncation limit, but these are minor gaps for this complexity level.

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?

Both parameters are already fully described in the input schema: pr_id as 'Pull request ID' and repo_slug as 'Repository slug'. The tool description adds no parameter-level meaning beyond this, so the baseline score of 3 applies.

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 and resource: 'Get the unified diff for a pull request.' It clearly distinguishes from sibling tools like get_pull_request by specifying the diff output and adding the unique truncation behavior.

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?

The description implies the clear usage context: retrieve the patch/diff content for a pull request. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of full guidance.

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