Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

List pull request changes

bb_get_pull_request_changes

Lists the file-level changes in a Bitbucket pull request, showing added, modified, and deleted paths for review or impact analysis.

Instructions

List the file-level changes of a pull request (added/modified/deleted paths).

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>",
      "pullRequestId": "<pullRequestId>"
    },
    "name": "bb_get_pull_request_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number (Cloud only; from nextPageStart of the previous call). Ignored on Server/DC.
limitNoPage size (1-1000).
startNoZero-based page offset (Server/DC).
projectKeyYesProject key (on Cloud: workspace slug).
pullRequestIdYesPull request id, e.g. 101.
repositorySlugYesRepository slug, e.g. 'service-api'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the shape of the returned content (added/modified/deleted paths), which is useful, but says nothing about pagination behavior across Cloud/Server, size limits on large PRs, or permission requirements. Adequate but incomplete for an unannotated read 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?

A single front-loaded sentence with the key scope information in the first clause and the clarifying detail immediately after. No filler, nothing to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter paginated list tool with no annotations and no output schema, the description covers what is returned but omits pagination expectations and the diff-vs-changes distinction. The schema handles parameter documentation well, so the remaining gap is modest but real.

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%, with all six parameters individually documented including the Cloud-only 'page' and Server/DC 'start' split. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('List the file-level changes of a pull request') and clarifies the granularity with the parenthetical '(added/modified/deleted paths)', which distinguishes it from a raw diff tool. It stops short of naming the sibling it is not (e.g. bb_get_pull_request_diff), so differentiation is implied rather than explicit.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternatives are named. The phrase 'file-level changes ... (added/modified/deleted paths)' implies this is the choice when you want a changed-file inventory rather than a textual diff, but the agent must infer that.

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