Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Update pull request

bb_update_pull_request

Update a pull request's title, description, or target branch. Specify only the fields to change; existing values are kept when a field is omitted.

Instructions

Update title, description or target branch of a pull request. Server/DC uses optimistic locking (re-fetch + one retry on 409); Cloud has no version field and applies a single partial PUT.

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_update_pull_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title (omit to keep current).
toBranchNoRetarget to this branch (omit to keep current).
projectKeyYesProject key (target repository; on Cloud: workspace slug).
descriptionNoNew description (omit to keep current).
pullRequestIdYesPull request id.
repositorySlugYesTarget repository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral value: it discloses that Server/DC performs optimistic locking with a re-fetch and one retry on 409, while Cloud applies a single partial PUT with no version field. That concurrency-conflict behavior is not derivable from the schema. It stops short of stating permission requirements, whether notifications are triggered, or what is returned.

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 sentences, front-loaded with the field scope and followed by the platform-specific behavior. No filler, no restatement of the title, and the distinction between Cloud and Server/DC is compressed into one clause.

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 6-parameter mutation tool with no annotations and no output schema, the description covers what can be changed and the platform locking/retry semantics, which is the non-obvious part. Missing pieces are the return value (updated PR representation?) and any permission or side-effect expectations.

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%, and each parameter already documents its own 'omit to keep current' semantics, so the schema does the heavy lifting. The description adds only the grouping of the three mutable fields, and does not explain platform-dependent meaning of projectKey (project key vs. Cloud workspace slug).

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 ('Update') and an explicitly bounded resource scope ('title, description or target branch of a pull request'), which rules out merge/decline/create siblings. It does not name any alternative tool, so the differentiation is by scope rather than by routing.

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?

Usage is implied by the narrow field list and the 'omit to keep current' semantics, so an agent can infer this is a partial edit. There is no explicit when-to-use/when-not guidance, no mention of required permissions, and no pointer to siblings like bb_merge_pull_request or bb_decline_pull_request for other state changes.

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