Fetch a Bitbucket pull request's metadata (title, state, author, branches, description, URL).

List pull requests in a Bitbucket repository. Filter by state, author UUID, or branch. Returns up to limit results sorted newest first.

Fetch the unified diff for a pull request. Returns the raw text diff, suitable for reviewing what the PR changes.

List all comments on a pull request, including general and inline (file+line) comments. Returns comments sorted oldest-first.

Get the status of pipelines triggered by this PR (most recent first), with each step's pass/fail state. Use this to find failing steps; then use get_pipeline_step_log to read logs.

Fetch the log output of a specific pipeline step. Use pipeline_uuid and step_uuid from get_pr_pipeline_status. Returns plain text log contents.

Post a general comment on a pull request (not tied to a specific file or line). For inline file/line comments, use add_pr_inline_comment.

Reply to an existing PR comment, creating a threaded reply. For inline comments, the path and line are inherited from the parent — do not use add_pr_inline_comment to reply, since that posts a sibling comment instead of a threaded reply.

Update a pull request's title, description (the PR Overview), and/or reviewers. Pass any combination — fields you omit are left unchanged. The description is interpreted as Markdown. reviewers replaces the full reviewer list with the given Bitbucket account UUIDs (including the curly braces); pass an empty array to clear all reviewers.

Mark a pull request as draft or ready for review. Pass draft: true to convert to draft, or draft: false to mark ready.

Mark a PR comment as resolved or unresolved. Defaults to resolved=true. Use list_pr_comments to see current resolution state.

Open a new pull request. source_branch defaults to the current git branch when run from inside a checkout. destination_branch defaults to the repository's configured main branch on Bitbucket. description is interpreted as Markdown. reviewers is a list of Bitbucket account UUIDs (including the curly braces).

Post a comment on a specific file and line within a pull request's diff. Use get_pr_diff first if you need to confirm line numbers are present in the diff. For general PR comments, use add_pr_comment.