Bitbucket PATCH Request
bb_patchPartially update Bitbucket resources such as pull requests, repositories, and comments. Specify the endpoint path and a partial JSON body to apply targeted changes without full payloads.
Instructions
Partially update Bitbucket resources. Returns TOON format by default.
IMPORTANT - Cost Optimization: Use jq param to filter response fields.
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Update PR title/description:
/repositories/{workspace}/{repo}/pullrequests/{id}body:{"title": "New title", "description": "Updated description"}Update PR reviewers:
/repositories/{workspace}/{repo}/pullrequests/{id}body:{"reviewers": [{"uuid": "{user-uuid}"}]}Update repository properties:
/repositories/{workspace}/{repo}body:{"description": "New description"}Update comment:
/repositories/{workspace}/{repo}/pullrequests/{pr_id}/comments/{comment_id}body:{"content": {"raw": "Updated comment"}}
The /2.0 prefix is added automatically. API reference: https://developer.atlassian.com/cloud/bitbucket/rest/
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The Bitbucket API endpoint path (without base URL). Must start with "/". Examples: "/workspaces", "/repositories/{workspace}/{repo_slug}", "/repositories/{workspace}/{repo_slug}/pullrequests/{id}" | |
| queryParams | No | Optional query parameters as key-value pairs. Examples: {"pagelen": "25", "page": "2", "q": "state=\"OPEN\"", "fields": "values.title,values.state"} | |
| jq | No | JMESPath expression to filter/transform the response. IMPORTANT: Always use this to extract only needed fields and reduce token costs. Examples: "values[*].{name: name, slug: slug}" (extract specific fields), "values[0]" (first result), "values[*].name" (names only). See https://jmespath.org | |
| outputFormat | No | Output format: "toon" (default, 30-60% fewer tokens) or "json". TOON is optimized for LLMs with tabular arrays and minimal syntax. | |
| body | Yes | Request body as a JSON object. Structure depends on the endpoint. Example for PR: {"title": "My PR", "source": {"branch": {"name": "feature"}}} |