Bitbucket MCP Server

update_pull_request

Update pull request title, description, or reviewers with version-based conflict prevention and auto-retry on conflicts.

Instructions

Update an existing pull request (title, description, reviewers). Accepts version from a prior read for conflict prevention; auto-refetches and retries once on 409 conflicts.

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

Input Schema

Name	Required	Description
`title`	No	New title for the pull request
`version`	No	Current version from a prior read (saves a fetch; auto-refetch + retry on 409)
`repoSlug`	Yes	The repository slug
`reviewers`	No	New list of reviewer usernames (replaces existing reviewers)
`projectKey`	Yes	The project key (e.g., PROJ)
`description`	No	New description/body for the pull request
`pullRequestId`	Yes	The pull request ID to update

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Jul 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Discloses the auto-refetch and retry behavior on 409 conflicts, which is useful. However, with no annotations, more behavioral details (e.g., required permissions, side effects if PR not found) would improve transparency.

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?

Two concise sentences with no wasted words. The first sentence frontloads the core purpose, and the second adds important behavioral detail. Every phrase 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?

Given the 7 parameters with full schema coverage and no output schema, the description is fairly complete for a mutation tool. It explains conflict handling but could mention the return value or additional side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 7 parameters with descriptions. The description adds specific context to the 'version' parameter (saves a fetch, auto-retry), which goes beyond the schema. No other parameters gain extra meaning from the description.

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?

Clearly states the verb 'Update' and the resource 'pull request', listing the fields that can be modified. Distinguishes from sibling tools like create_pull_request, merge_pull_request, and decline_pull_request by specifying it is for an existing PR.

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?

Provides clear context on when to use this tool (updating an existing PR) and includes a key usage detail about the version parameter for conflict prevention. Does not explicitly state when not to use or mention specific alternatives beyond implied actions.

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