# Bitbucket Bitbucket is a Git-based code hosting and collaboration platform supporting private and public repositories, enabling teams to manage and review code through pull requests and integrations - **Category:** developer tools - **Auth:** OAUTH2 - **Composio Managed App Available?** Yes - **Tools:** 104 - **Triggers:** 0 - **Slug:** `BITBUCKET` - **Version:** 20260316_00 ## Tools ### Approve Pull Request **Slug:** `BITBUCKET_APPROVE_PULL_REQUEST` Tool to approve a pull request as the authenticated user. Use when you need to formally approve changes in a pull request review process. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `pull_request_id` | integer | Yes | The ID of the pull request to approve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Browse repository path **Slug:** `BITBUCKET_BROWSE_REPOSITORY_PATH` Tool to retrieve content for a file path or browse directory contents at a specified revision in a Bitbucket repository. Use when you need flexible access to repository content - returns raw file data for files or paginated directory listings for directories. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Filter query string using Bitbucket's REST API filtering syntax to narrow results. Only applicable when browsing directories. | | `page` | integer | No | Page number for paginated results (starts from 1). Only applicable when browsing directories. | | `path` | string | No | File or directory path within the repository to browse. Use empty string for root directory. | | `sort` | string | No | Field name for sorting results. Prefix with '-' for descending order. Only applicable when browsing directories. | | `commit` | string | No | Commit hash, branch name, or tag to browse from. Defaults to 'master' if not specified. | | `format` | string | No | Response format. Use 'meta' to return metadata as JSON instead of raw file contents when browsing a file. | | `pagelen` | integer | No | Number of entries per page (1-100). Only applicable when browsing directories. Controls pagination size. | | `max_depth` | integer | No | Maximum depth for breadth-first recursive directory traversal. Only applicable when path is a directory. Large values may cause timeouts. | | `repo_slug` | string | Yes | Repository slug or UUID (typically URL-formatted name). | | `workspace` | string | Yes | Workspace ID or UUID (often username or team name) containing the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create a branch **Slug:** `BITBUCKET_CREATE_BRANCH` Creates a new branch in a Bitbucket repository from a target commit hash; the branch name must be unique, adhere to Bitbucket's naming conventions, and not include the 'refs/heads/' prefix. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name for the new branch (e.g., 'feature/new-login', 'bugfix/issue-123'). Important: Do not include the 'refs/heads/' prefix. | | `repo_slug` | string | Yes | The slug or UUID of the repository where the branch will be created. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or UUID that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | | `target_hash` | string | Yes | The full commit hash (SHA1) from which the new branch will be created. This commit must exist in the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create an issue **Slug:** `BITBUCKET_CREATE_ISSUE` Creates a new issue in a Bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component IDs exist. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `kind` | string | No | Type of the issue (e.g., 'bug', 'enhancement', 'proposal', 'task'). | | `title` | string | Yes | Title for the new issue. | | `due_on` | string | No | Due date for the issue in ISO 8601 format (e.g., 'YYYY-MM-DDTHH:mm:ssZ'). | | `content` | string | Yes | Detailed description for the new issue. | | `assignee` | string | No | Bitbucket username of the assignee. The assignee must have repository access. | | `priority` | string | No | Priority level of the issue (e.g., 'trivial', 'minor', 'major', 'critical', 'blocker'). | | `repo_slug` | string | Yes | The slug of the Bitbucket repository. | | `workspace` | string | Yes | The ID or slug of the Bitbucket workspace. | | `version_id` | integer | No | Numeric ID of an existing version to associate with this issue. | | `component_id` | integer | No | Numeric ID of an existing component to associate with this issue. | | `milestone_id` | integer | No | Numeric ID of an existing milestone to associate with this issue. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create an issue comment **Slug:** `BITBUCKET_CREATE_ISSUE_COMMENT` Adds a new comment with markdown support to an existing Bitbucket issue. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `content` | string | Yes | The raw text content for the comment. This content supports markdown formatting, which Bitbucket will then render. | | `issue_id` | string | Yes | The unique identifier of the issue on which the comment will be posted. | | `repo_slug` | string | Yes | The slug (URL-friendly version) of the repository name. | | `workspace` | string | Yes | The ID or slug of the workspace or user that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create a pull request **Slug:** `BITBUCKET_CREATE_PULL_REQUEST` Creates a new pull request in a specified Bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | Concise title summarizing the changes for the pull request. | | `repo_slug` | string | Yes | Slug (URL-friendly name) of the repository for the pull request. | | `reviewers` | array | No | List of Bitbucket user UUIDs to be added as reviewers. Malformed or non-existent UUIDs trigger validation errors. | | `workspace` | string | Yes | Workspace ID (UUID or slug) of the repository owner. | | `description` | string | No | Detailed Markdown description of the pull request, outlining changes and purpose. | | `source_branch` | string | Yes | Name of the source branch with changes to be merged. | | `destination_branch` | string | No | Name of the destination branch for merging; defaults to repository's main branch if unspecified. | | `close_source_branch` | boolean | No | If true, automatically closes the source branch upon pull request merge. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create pull request comment **Slug:** `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` Creates a new comment on a Bitbucket pull request. Supports top-level comments, threaded replies, and inline code comments. Use when providing feedback on a PR, replying to existing comments, or commenting on specific code lines. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `inline` | object | No | Location details for inline code comments. | | `repo_slug` | string | Yes | The slug (URL-friendly version) of the repository name. | | `workspace` | string | Yes | The ID or slug of the workspace that owns the repository. | | `content_raw` | string | Yes | The raw text content for the comment. Supports markdown formatting which Bitbucket will render. | | `content_markup` | string | No | The markup language used for the content. Defaults to 'markdown'. | | `pull_request_id` | string | Yes | The unique identifier of the pull request to comment on. | | `parent_comment_id` | integer | No | ID of an existing comment to reply to, creating a threaded comment. If omitted, creates a top-level comment. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create commit report annotations **Slug:** `BITBUCKET_CREATE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONS` Adds multiple annotations to a commit report in bulk. Use when you need to add code analysis findings (vulnerabilities, code smells, bugs) to a report attached to a specific commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to which the report belongs. This is the full SHA-1 commit identifier. | | `reportId` | string | Yes | The unique identifier of the report to which annotations will be added. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) that contains the commit. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | | `annotations` | array | Yes | Array of annotation objects to be added to the report. Each annotation must have path, line, summary, and severity. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List commits from revision (POST) **Slug:** `BITBUCKET_CREATE_REPOSITORIES_COMMITS2` Tool to list commits from a revision using POST method. Identical to GET endpoint but allows sending include/exclude parameters in request body to avoid URL length limits. Use when include/exclude parameters are too long for query strings. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `path` | string | No | Optional file path to filter commits. Only commits that modified this file or directory will be returned. | | `exclude` | string | No | Optional commit hash or branch to exclude from the results. Can be used to create a range with the 'include' parameter. Use POST method when this value is very long. | | `include` | string | No | Optional commit hash or branch to include in the results. Can be used to create a range with the 'exclude' parameter. Use POST method when this value is very long. | | `pagelen` | integer | No | Number of commits per page (1-100). Bitbucket default is typically 30 if not specified. | | `revision` | string | Yes | The commit hash, branch name, tag, or other revision identifier to start listing commits from. Commits are returned in reverse chronological order starting from this revision. | | `repo_slug` | string | Yes | The slug of the repository. This is the repository's name, usually in lowercase and with hyphens instead of spaces. | | `workspace` | string | Yes | The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create repository **Slug:** `BITBUCKET_CREATE_REPOSITORY` Creates a new Bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project_key` is not provided. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `has_wiki` | boolean | No | Enable the wiki (`True`), or disable it (`False`). | | `language` | string | No | Primary programming language (e.g., 'python', 'java') for categorization. | | `repo_slug` | string | Yes | URL-friendly slug for the new repository. | | `workspace` | string | Yes | Workspace identifier. Can be a slug (e.g., 'my-workspace') or UUID with curly braces (e.g., '{uuid}'). Bare UUIDs without braces are automatically normalized to the required format. | | `has_issues` | boolean | No | Enable the issue tracker (`True`), or disable it (`False`). | | `is_private` | boolean | No | Repository visibility: `True` for private, `False` for public. | | `description` | string | No | Description for the new repository. | | `fork_policy` | string ("allow_forks" | "no_public_forks" | "no_forks") | No | Forking policy for the repository, determining who can create forks. | | `project_key` | string | No | Key of the Bitbucket project for the repository; if omitted, it's placed in the workspace's oldest project. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create snippet comment **Slug:** `BITBUCKET_CREATE_SNIPPET_COMMENT` Posts a new top-level comment or a threaded reply to an existing comment on a specified Bitbucket snippet. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `content` | string | Yes | Raw text content of the comment; Bitbucket will render any included markup (like Markdown). | | `parent_id` | integer | No | ID of an existing comment to reply to, creating a threaded comment; if omitted, a top-level comment is created. | | `workspace` | string | Yes | Workspace ID or slug (e.g., 'my_workspace_slug' or a UUID) for the Bitbucket workspace containing the snippet. | | `encoded_id` | string | Yes | Unique, encoded ID of the Bitbucket snippet to comment on (typically part of the snippet's URL). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create team pipeline variable **Slug:** `BITBUCKET_CREATE_TEAMS_PIPELINES_CONFIG_VARIABLES` Creates a team-level pipeline configuration variable in Bitbucket. Use when you need to add environment variables or configuration values that should be available to all pipelines within a team. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The name/key of the pipeline variable. Must be unique within the team's pipeline configuration. | | `value` | string | Yes | The value of the pipeline variable. This will be available to all pipelines in the team. | | `secured` | boolean | No | Whether the variable should be secured (masked in logs). Set to `True` for sensitive values like passwords or API keys, `False` for non-sensitive values. | | `username` | string | Yes | The team username that owns the pipeline configuration. This is the team identifier in Bitbucket. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create user pipeline variable **Slug:** `BITBUCKET_CREATE_USERS_PIPELINES_CONFIG_VARIABLES` Creates a user-level pipeline variable for Bitbucket pipelines. Use when you need to create account-level configuration variables that can be used across all repositories owned by the user. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The name/key of the pipeline variable. Must be unique for the user. | | `value` | string | Yes | The value of the pipeline variable. | | `secured` | boolean | No | Whether the variable should be secured/encrypted (true) or stored as plain text (false). Defaults to false. | | `selected_user` | string | Yes | The UUID or username of the user. When using UUID format, it should be URL-encoded (e.g., %7B4f3ecac3-c951-41d4-8a4c-95f40be978fc%7D for {4f3ecac3-c951-41d4-8a4c-95f40be978fc}). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete commit comment **Slug:** `BITBUCKET_DELETE_COMMIT_COMMENT` Permanently deletes a specific comment on a commit. Use when removing outdated, incorrect, or unwanted feedback on a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash (SHA) or commit reference. This identifies the commit that has the comment to be deleted. | | `repo_slug` | string | Yes | The slug of the repository. This is the repository's name, usually in lowercase and with hyphens instead of spaces. | | `workspace` | string | Yes | The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier. | | `comment_id` | string | Yes | The unique identifier of the comment to be deleted from the specified commit. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete issue **Slug:** `BITBUCKET_DELETE_ISSUE` Permanently deletes a specific issue, identified by its `issue_id`, from the repository specified by `repo_slug` within the given `workspace`. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `issue_id` | string | Yes | The unique identifier of the issue to be deleted from the specified repository. | | `repo_slug` | string | Yes | The slug of the repository. This is the repository's name, usually in lowercase and with hyphens instead of spaces. | | `workspace` | string | Yes | The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete pull request comment **Slug:** `BITBUCKET_DELETE_PULL_REQUEST_COMMENT` Permanently deletes a specific pull request comment (top-level, inline, or threaded reply). Use when removing outdated, incorrect, or unwanted feedback from a pull request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug of the repository. This is the repository's name, usually in lowercase and with hyphens instead of spaces. | | `workspace` | string | Yes | The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier. | | `comment_id` | integer | Yes | The unique identifier of the comment to be deleted from the pull request. This can be a top-level comment, inline comment, or threaded reply. | | `pull_request_id` | integer | Yes | The unique identifier of the pull request containing the comment to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete commit report annotation **Slug:** `BITBUCKET_DELETE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONS` Deletes a single annotation matching the provided ID from a commit report. Use when you need to remove a specific annotation from a code analysis report. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to which the report belongs. This is the full SHA-1 commit identifier. | | `reportId` | string | Yes | The unique identifier of the report that contains the annotation. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) that contains the commit. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | | `annotationId` | string | Yes | The unique identifier of the annotation to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete repository **Slug:** `BITBUCKET_DELETE_REPOSITORY` Permanently deletes a specified Bitbucket repository; this action is irreversible and does not affect forks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug (URL-friendly name) of the repository to be deleted. This identifies the repository within the workspace. | | `workspace` | string | Yes | The ID or slug of the Bitbucket workspace that owns the repository. This can be a user's username or a team's slug. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete snippet watch **Slug:** `BITBUCKET_DELETE_SNIPPETS_WATCH` Stops watching a specific snippet. Use when you want to unsubscribe from notifications for a snippet. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workspace` | string | Yes | The workspace ID (slug) or the workspace UUID surrounded by curly braces, identifying the Bitbucket workspace. | | `encoded_id` | string | Yes | The unique identifier (encoded ID) of the snippet to stop watching. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete user pipeline variable **Slug:** `BITBUCKET_DELETE_USER_PIPELINE_VARIABLE` Permanently deletes a user-level pipeline configuration variable identified by its UUID. Use this to remove pipeline variables that are no longer needed at the account level. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `username` | string | Yes | The username of the Bitbucket account that owns the pipeline variable. This is the account identifier. | | `variable_uuid` | string | Yes | The UUID of the pipeline variable to delete. This must be in UUID format (e.g., b070fa8a-c3db-42bd-870c-dea7c980c7b8) and can be optionally wrapped in curly braces. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get branch **Slug:** `BITBUCKET_GET_BRANCH` Retrieves detailed information about a specific branch in a Bitbucket repository. Use when you need to get branch metadata, the commit it points to, or verify a branch exists. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name of the branch to retrieve (e.g., 'master', 'main', 'feature/my-feature'). Do not include the 'refs/heads/' prefix. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Commit Build Status **Slug:** `BITBUCKET_GET_COMMIT_BUILD_STATUS` Get a specific build status for a commit in Bitbucket. Use when you need to check the status of a particular build/CI run for a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The unique key identifying the specific build status. | | `commit` | string | Yes | The commit hash to get the build status for. | | `repo_slug` | string | Yes | The slug or UUID of the repository. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Commit Changes **Slug:** `BITBUCKET_GET_COMMIT_CHANGES` Tool to retrieve a page of changes made in a specified commit, showing all changed files with their change statistics (lines added/removed, status). Use when you need to enumerate files modified in a specific commit or commit range. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `spec` | string | Yes | Commit SHA or range (e.g., '3a8b42' for single commit or '3a8b42..9ff173' for range). | | `pagelen` | integer | No | Number of changes per page (1-100). Bitbucket default is 500 if not specified. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get commit comment **Slug:** `BITBUCKET_GET_COMMIT_COMMENT` Retrieves a specific comment from a commit by its ID. Use when you need to fetch details of a particular commit comment including content, author, timestamps, and inline location. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to retrieve the comment from. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. | | `comment_id` | integer | Yes | The unique identifier for the comment. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Commit Diff **Slug:** `BITBUCKET_GET_COMMIT_DIFF` Tool to retrieve the unified diff between two provided revisions or for a single commit in a Bitbucket repository. Use when you need to see the actual code changes in a commit or between two commits. Supports filtering by file path and various diff options. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `path` | string | No | Optional file path to filter the diff to a specific file or directory. If omitted, returns diff for all changes. | | `spec` | string | Yes | A commit SHA, branch name, tag, or revspec (e.g. '3a8b42..9ff173' for range). For a single commit, provide the commit hash. For comparing two commits, use 'commit1..commit2' format. | | `merge` | boolean | No | Whether to generate merge diff. Set to true for merge commit diffs. | | `topic` | boolean | No | Whether to generate a 2-way three-dot diff when spec contains two commits. Set to true to use three-dot diff notation. | | `binary` | boolean | No | Whether to include binary file diffs. Set to true to include binary diffs in the output. | | `context` | integer | No | Number of context lines to include around changes. If not specified, uses the default context lines. | | `renames` | boolean | No | Whether to detect file renames. Set to true to show rename detection in the diff. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace ID or username that owns the repository. | | `ignore_whitespace` | boolean | No | Whether to ignore whitespace changes in the diff. Set to true to exclude whitespace-only changes. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get current user (v2) **Slug:** `BITBUCKET_GET_CURRENT_USER2` Tool to retrieve complete profile information for the currently authenticated Bitbucket user. Use when you need comprehensive user details including account_id, username, nickname, and other profile fields. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get deployment environment variables **Slug:** `BITBUCKET_GET_DEPLOYMENT_ENVIRONMENT_VARIABLES` Retrieves deployment environment level variables for a specific Bitbucket repository environment. Use when you need to view or audit environment-specific configuration variables for deployments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | | `environment_uuid` | string | Yes | The UUID of the deployment environment. Must be provided with curly braces (e.g., {2e1c3c19-12f2-4e9b-9ed7-45512af9a7ce}). The API will handle URL-encoding automatically. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get file from repository **Slug:** `BITBUCKET_GET_FILE_FROM_REPOSITORY` Retrieves a specific file's content from a Bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `path` | string | Yes | Full path to the file within the repository (e.g., 'src/main.py'). | | `commit` | string | Yes | Commit hash, branch name (fetches latest), or tag for the file version. | | `repo_slug` | string | Yes | Repository slug or UUID (typically URL-formatted name). | | `workspace` | string | Yes | Workspace ID or UUID (often username or team name) containing the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get hook events **Slug:** `BITBUCKET_GET_HOOK_EVENTS` Retrieves a paginated list of all valid webhook events for a specified entity type (repository or workspace). Use when you need to discover available webhook event types for subscription or webhook configuration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `subject_type` | string ("repository" | "workspace") | Yes | The type of entity for which to retrieve available webhook events. Use 'repository' for repository-level events or 'workspace' for workspace-level events. Note: team and user webhooks are deprecated; use workspace instead. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get OpenID configuration for OIDC in Pipelines **Slug:** `BITBUCKET_GET_OPENID_CONFIGURATION` Retrieves the OpenID Connect discovery configuration for Bitbucket Pipelines OIDC. Use when integrating Bitbucket Pipelines with resource servers (AWS, GCP, Vault) using OpenID Connect authentication. Returns issuer URL, JWKS URI, and supported capabilities. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workspace` | string | Yes | The workspace identifier (workspace slug or UUID). This identifies the Bitbucket workspace for which to retrieve the OIDC configuration. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Pull Request **Slug:** `BITBUCKET_GET_PULL_REQUEST` Get a single pull request by ID with complete details. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). Must exactly match the pull request's workspace (case-sensitive); slug and UUID are not interchangeable. | | `pull_request_id` | integer | Yes | The ID of the pull request to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get pull request comment **Slug:** `BITBUCKET_GET_PULL_REQUEST_COMMENT` Tool to retrieve a specific comment from a pull request by its ID. Use when you need to fetch details of a particular pull request comment including content, author, timestamps, and inline location. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. | | `comment_id` | integer | Yes | The unique identifier for the comment. | | `pull_request_id` | integer | Yes | The unique identifier of the pull request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Pull Request Commits **Slug:** `BITBUCKET_GET_PULL_REQUEST_COMMITS` Tool to retrieve commits for a specified pull request. Use when reviewing the commit history of a PR or analyzing changes included in a pull request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of commits per page (1-100). Bitbucket default is 30 if not specified. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `pull_request_id` | integer | Yes | The ID of the pull request to retrieve commits for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Pull Request Diff **Slug:** `BITBUCKET_GET_PULL_REQUEST_DIFF` Tool to fetch the unified diff for a Bitbucket pull request (follows 302 redirect to repository diff). Use when reviewing code changes in a PR. Supports optional truncation for large diffs via max_chars parameter. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `max_chars` | integer | No | Maximum number of characters to return in the diff. If the diff exceeds this limit, it will be truncated. If None, no truncation is applied. Use this to protect against very large diffs. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `pull_request_id` | integer | Yes | The ID of the pull request to retrieve the diff for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Pull Request Diffstat **Slug:** `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` Tool to get the diffstat for a Bitbucket pull request, showing all changed files with their change statistics (lines added/removed, status). Use when you need to enumerate files modified in a PR. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of diffstat entries per page (1-100). Bitbucket default is 500 if not specified. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `pull_request_id` | integer | Yes | The ID of the pull request to get diffstat for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get raw file content **Slug:** `BITBUCKET_GET_RAW_FILE_CONTENT` DEPRECATED: Use BITBUCKET_GET_FILE_FROM_REPOSITORY instead. Tool to retrieve the raw content of a file from a Bitbucket repository at a specified commit, branch, or tag. Use when you need to read file contents from a specific revision. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `path` | string | Yes | The file path including filename and extension (e.g., 'src/main.py' or 'README.md'). | | `commit` | string | Yes | The commit SHA, branch name, or tag name to retrieve the file from. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) where the file is located. | | `workspace` | string | Yes | The workspace ID or username that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Repository Branching Model **Slug:** `BITBUCKET_GET_REPOSITORIES_BRANCHING_MODEL` Return the branching model as applied to the repository. Use when you need to understand the repository's branch workflow configuration, including development/production branches and branch type prefixes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug. | | `workspace` | string | Yes | This can either be the workspace ID (slug) or the workspace UUID surrounded by curly-braces. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Repository Commit **Slug:** `BITBUCKET_GET_REPOSITORIES_COMMIT` Tool to retrieve detailed information about a specific commit in a Bitbucket repository. Use when you need to get complete commit details including author, message, date, parents, and related links. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash (SHA) to retrieve. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get commit comments **Slug:** `BITBUCKET_GET_REPOSITORIES_COMMIT_COMMENTS` Retrieves all comments on a specific commit in a Bitbucket repository. Returns both global and inline code comments. Use when you need to view feedback, discussions, or notes left on a specific commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for pagination. Defaults to 1 if not specified. | | `commit` | string | Yes | The commit hash/SHA to retrieve comments for. | | `pagelen` | integer | No | Number of items per page for pagination. Defaults to 10 if not specified. | | `repo_slug` | string | Yes | The slug (URL-friendly version) of the repository name. | | `workspace` | string | Yes | The ID or slug of the workspace that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get commit report **Slug:** `BITBUCKET_GET_REPOSITORIES_COMMIT_REPORT` Returns a single report matching the provided ID from a commit. Use when you need to retrieve details of a specific analysis report (e.g., security scan, code coverage, test results, or bug report) for a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to which the report belongs. This is the full SHA-1 commit identifier. | | `reportId` | string | Yes | Either the uuid or external-id of the report to retrieve. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) that contains the commit. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Commit Reports **Slug:** `BITBUCKET_GET_REPOSITORIES_COMMIT_REPORTS` Tool to get reports linked to a specific commit. Use when you need to retrieve analysis results, test reports, security scans, or code coverage data associated with a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to retrieve reports for. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get commit report annotation **Slug:** `BITBUCKET_GET_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONS` Returns a single annotation matching the provided ID from a commit report. Use when you need to retrieve details of a specific code analysis finding (e.g., vulnerability, code smell, or bug) identified in a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to which the report belongs. This is the full SHA-1 commit identifier. | | `reportId` | string | Yes | Either the uuid or external-id of the report that contains the annotation. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) that contains the commit. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | | `annotationId` | string | Yes | Either the uuid or external-id of the annotation to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get commit statuses **Slug:** `BITBUCKET_GET_REPOSITORIES_COMMIT_STATUSES` Returns all build statuses (e.g., CI/CD pipeline results) for a specific commit. Use when you need to check build status, verify test results, or monitor deployment pipelines for a particular commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash (SHA) to retrieve statuses for. Can be full or abbreviated hash. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get effective branching model **Slug:** `BITBUCKET_GET_REPOSITORIES_EFFECTIVE_BRANCHING_MODEL` Retrieves the effective branching model for a Bitbucket repository, showing which branching model is currently applied (including any inheritance from project-level settings). Use when you need to understand the repository's branch workflow configuration, including development and production branches and branch type prefixes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Repository Environment **Slug:** `BITBUCKET_GET_REPOSITORIES_ENVIRONMENTS2` Retrieve detailed information about a specific deployment environment in a Bitbucket repository. Use when you need to get environment configuration, deployment settings, or check environment properties like locks and restrictions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug or UUID of the repository. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. | | `environment_uuid` | string | Yes | The UUID of the environment to retrieve. Must include curly braces (e.g., {2e1c3c19-12f2-4e9b-9ed7-45512af9a7ce}). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get file commit history **Slug:** `BITBUCKET_GET_REPOSITORIES_FILEHISTORY` Returns a paginated list of commits that modified the specified file. Use when you need to track file changes over time, find who modified a file, or determine when a file was created or last changed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string for filtering commits in the file history. Common use: filter by commit date using 'commit.date<=YYYY-MM-DD' or 'commit.date>=YYYY-MM-DD'. Example: 'commit.date<=2024-12-31' returns only commits before that date. | | `page` | integer | No | Page number for paginated results (starts from 1). | | `path` | string | Yes | Full path to the file within the repository (e.g., 'README.md', 'src/main.py'). | | `commit` | string | Yes | Commit hash, branch name, or tag from which to retrieve file history. The API returns commits reachable from this reference that modified the file. | | `fields` | string | No | Comma-separated list of fields to include or exclude from the response. Prefix with '+' to add fields or '-' to remove them. Example: '+values.commit.message' adds commit messages to the response. | | `pagelen` | integer | No | Number of commits per page (1-100). Default is typically 30 if not specified. | | `renames` | boolean | No | Whether to follow file renames through history. If true (default), returns commits that modified the file even if it had a different name. If false, only returns commits where the file had the current path. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) or UUID. | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Check if user voted for issue **Slug:** `BITBUCKET_GET_REPOSITORIES_ISSUES_VOTE` Tool to check whether the authenticated user has voted for a specific issue in a Bitbucket repository. Use when you need to verify if the current user has already voted on an issue before attempting to vote or unvote. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `issue_id` | integer | Yes | The numeric ID of the issue to check vote status for. | | `repo_slug` | string | Yes | The slug (URL-friendly name) of the repository. | | `workspace` | string | Yes | The workspace ID or slug (URL-friendly name) that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Repositories Merge Base **Slug:** `BITBUCKET_GET_REPOSITORIES_MERGE_BASE` Get the merge base (best common ancestor) between two commits in a Bitbucket repository. Use when you need to find the common ancestor commit between two branches or commits for comparison or merge operations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `revspec` | string | Yes | Two commit hashes separated by '..' (e.g., '3a8b42..9ff173' or 'abc123..def456'). This specifies the two commits to find the best common ancestor between. | | `repo_slug` | string | Yes | The slug or UUID of the repository. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get specific pipeline **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES2` Retrieve a specified pipeline from a Bitbucket repository. Use when you need to get detailed information about a specific pipeline execution including its status, build number, and results. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug (URL-friendly name) or UUID. | | `workspace` | string | Yes | The workspace ID (slug) or workspace UUID that owns the repository. | | `pipeline_uuid` | string | Yes | The pipeline UUID to retrieve. Must be in UUID format, typically enclosed in curly braces. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository pipelines caches **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_CACHES` Retrieves the repository pipelines caches. Use when you need to list all caches configured for Bitbucket Pipelines in a specific repository. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository pipeline runners **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_RUNNERS` Retrieves the list of self-hosted runners configured for a repository's pipelines. Use when you need to view available runners for pipeline execution. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug (URL-friendly identifier) for the repository. | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. This can be the workspace slug (e.g., 'my-workspace') or its UUID enclosed in curly braces (e.g., '{workspace-uuid}'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository pipeline schedules **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_SCHEDULES` Retrieves configured pipeline schedules for a Bitbucket repository. Use when you need to view scheduled pipeline runs and their cron patterns. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug or identifier of the repository. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository SSH known hosts **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_SSH_KNOWN_HOSTS` Retrieves repository-level SSH known hosts configured for Bitbucket Pipelines. Use when you need to list or verify SSH known hosts that Pipelines can connect to during builds. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug (URL-friendly identifier) for the repository. | | `workspace` | string | Yes | The workspace slug or UUID. This identifies the Bitbucket workspace that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository pipeline variables **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_VARIABLES` Retrieves repository-level pipeline variables for a specific Bitbucket repository. Use when you need to view or audit pipeline configuration variables that are scoped to a repository. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string for filtering results using Bitbucket Query Language (BBQL). | | `page` | integer | No | Page number for pagination. Use this to retrieve subsequent pages of results. | | `sort` | string | No | Field to sort results by. Prefix with a hyphen (-) for descending order. | | `pagelen` | integer | No | Number of items to return per page. Controls the size of the paginated response. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get pipeline steps **Slug:** `BITBUCKET_GET_REPOSITORIES_PIPELINES_STEPS` Retrieves all steps for a given pipeline. Use when you need to inspect the individual steps of a pipeline execution, including their state, duration, and commands. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | | `pipeline_uuid` | string | Yes | The UUID of the pipeline. Must be enclosed in curly braces (e.g., '{f5500ca2-b74d-4e6a-84bf-5d2f73695152}'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get pull requests activity log **Slug:** `BITBUCKET_GET_REPOSITORIES_PULLREQUESTS_ACTIVITY` Get paginated activity log for all pull requests in a repository. Returns comments, updates, approvals, and request changes. Use when you need to track pull request activity history. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of activity entries per page (1-50). Bitbucket default is 20 if not specified. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace ID or slug (URL-friendly name). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get pull request comments **Slug:** `BITBUCKET_GET_REPOSITORIES_PULLREQUESTS_COMMENTS` Retrieves a paginated list of comments on a specific pull request in a Bitbucket repository. Returns global, inline, and threaded comments. Use when you need to view feedback, discussions, or reviews left on a pull request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for pagination. Defaults to 1 if not specified. | | `sort` | string | No | Sort order for results. Default is oldest to newest. Use '-created_on' for newest to oldest. | | `pagelen` | integer | No | Number of items per page for pagination. Defaults to 10 if not specified. | | `repo_slug` | string | Yes | The slug (URL-friendly version) of the repository name. | | `workspace` | string | Yes | The ID or slug of the workspace that owns the repository. | | `pull_request_id` | integer | Yes | The pull request ID to retrieve comments for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get pull request statuses **Slug:** `BITBUCKET_GET_REPOSITORIES_PULLREQUESTS_STATUSES` Returns all build statuses (e.g., CI/CD pipeline results) for a specific pull request. Use when you need to check build status, verify test results, or monitor deployment pipelines for a pull request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of statuses per page (1-100). Bitbucket default is 30 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | | `pull_request_id` | integer | Yes | The ID of the pull request to retrieve statuses for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository refs **Slug:** `BITBUCKET_GET_REPOSITORIES_REFS` Returns the branches and tags in the repository. Use when you need to list all refs (both branches and tags) in a single API call with optional filtering by type, name pattern, or commit hash. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string using Bitbucket Query Language (BBQL) to filter refs. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal). String values MUST be enclosed in double quotes. Filter by name pattern using 'name~"pattern"', by type using 'type="branch"' or 'type="tag"', or by commit hash using 'target.hash="hash"'. Examples: 'name~"feature/"' (refs starting with feature/), 'type="branch"' (only branches), 'type="tag"' (only tags), 'target.hash="a1b2c3d4"' (refs pointing to specific commit). Combine multiple conditions with AND/OR (e.g., 'type="branch" AND name~"feature/"'). | | `page` | integer | No | Page number for paginated results (starts from 1). | | `sort` | string | No | Field for sorting ref results. Prefix with '-' for descending order. Common sortable fields: 'name', 'target.date' (commit date). Default sorting applies natural sorting for ref names with numeric values. | | `pagelen` | integer | No | Number of refs per page (1-100). Bitbucket default is typically 10 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get tag **Slug:** `BITBUCKET_GET_REPOSITORIES_REFS_TAGS` Retrieves detailed information about a specific tag in a Bitbucket repository. Use when you need to get tag metadata, target commit details, or verify a tag exists. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name of the tag to retrieve (without refs/tags/ prefix). For example, 'v1.0.0' or 'fedex17'. | | `repo_slug` | string | Yes | The slug (URL-friendly name) of the repository. This identifies the repository within the workspace. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repositories src **Slug:** `BITBUCKET_GET_REPOSITORIES_SRC` Lists the contents of the root directory on the repository's main branch without needing to specify a commit or branch. This endpoint redirects to the main branch automatically. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `format` | string | No | Optional format parameter. Use 'meta' to get metadata instead of raw contents when accessing files. | | `repo_slug` | string | Yes | The repository slug (URL-friendly repository name). | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository watchers **Slug:** `BITBUCKET_GET_REPOSITORIES_WATCHERS` Retrieves a paginated list of all the watchers on the specified repository. Use when you need to see who is watching a particular repository. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug (URL-friendly identifier) for the repository. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This is the user-friendly identifier or UUID for the workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get repository **Slug:** `BITBUCKET_GET_REPOSITORY` Retrieves detailed information about a specific repository in a Bitbucket workspace. Use when you need to get repository metadata, settings, or details. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | The repository slug (URL-friendly identifier) for the repository to retrieve. | | `workspace` | string | Yes | The workspace slug or UUID. This identifies the Bitbucket workspace that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Repository Patch **Slug:** `BITBUCKET_GET_REPOSITORY_PATCH` Tool to retrieve the git patch content for a Bitbucket repository at a specified revision or commit range. Use when you need to review code changes, generate diffs, or analyze modifications between commits. Returns raw patch in unified diff format. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `spec` | string | Yes | A commit hash, branch name, tag, or commit range (e.g., '3a8b42..9ff173'). If a single commit is provided, the diff is against its first parent. For ranges, shows diff between the two commits. | | `max_chars` | integer | No | Maximum number of characters to return in the patch. If the patch exceeds this limit, it will be truncated. If None, no truncation is applied. Use this to protect against very large patches. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get snippet **Slug:** `BITBUCKET_GET_SNIPPET` Retrieves a specific Bitbucket snippet by its encoded ID from an existing workspace, returning its metadata and file structure. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workspace` | string | Yes | The workspace ID (slug) or the workspace UUID surrounded by curly braces, identifying the Bitbucket workspace. | | `encoded_id` | string | Yes | The unique identifier (encoded ID) of the snippet to be retrieved. | | `accept_format` | string | No | The desired format for the response. Valid options are 'application/json', 'multipart/related', or 'multipart/form-data'. This may affect how snippet content or file data is presented. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get snippet watch status **Slug:** `BITBUCKET_GET_SNIPPETS_WATCH` Checks if the current user is watching a specific snippet. Use when you need to verify watch status for a snippet. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workspace` | string | Yes | The workspace ID (slug) or the workspace UUID surrounded by curly braces, identifying the Bitbucket workspace. | | `encoded_id` | string | Yes | The unique identifier (encoded ID) of the snippet to check watch status for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get SSH keys for user **Slug:** `BITBUCKET_GET_SSH_LATEST_KEYS` Retrieves a paginated list of SSH keys for a specified Bitbucket user. Use when you need to view or audit SSH keys configured for a user account. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | The page number for pagination. Starts at 1. | | `pagelen` | integer | No | Number of SSH keys to return per page. Default is typically 10. | | `username` | string | Yes | The username of the Bitbucket user to retrieve SSH keys for. This is the account username (slug), not the display name or UUID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user **Slug:** `BITBUCKET_GET_USER` Retrieves public profile information for a specific Bitbucket user by username or UUID. Use when you need to get user details like display name, avatar, creation date, and links to related resources. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `selected_user` | string | Yes | The username or UUID of the user to retrieve. Can be a username (e.g., 'john_doe') or a UUID enclosed in curly braces (e.g., '{4f3ecac3-c951-41d4-8a4c-95f40be978fc}'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user emails **Slug:** `BITBUCKET_GET_USER_EMAILS` Returns all the authenticated user's email addresses, both confirmed and unconfirmed. Use when you need to retrieve all email addresses associated with the current user's account. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user email details **Slug:** `BITBUCKET_GET_USER_EMAILS2` Retrieves details about a specific email address for the authenticated user. Use when you need to check if an email is primary, confirmed, or verify email ownership. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `email` | string | Yes | The email address to retrieve details for. Must be one of the authenticated user's email addresses. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user permissions for repositories **Slug:** `BITBUCKET_GET_USER_PERMISSIONS_REPOSITORIES` Returns an object for each repository the caller has explicit access to, including their permission level. Use when you need to discover which repositories the authenticated user can access and their specific permissions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results. Used to retrieve a specific page in a multi-page result set. Page numbers start at 1. | | `pagelen` | integer | No | Number of items to return per page for pagination. Controls the size of the paginated result set. Default is typically 10 if not specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user permissions for workspaces **Slug:** `BITBUCKET_GET_USER_PERMISSIONS_WORKSPACES` Retrieves workspace memberships and permission levels for the authenticated user. Returns an object for each workspace the caller is a member of, along with their effective role (highest privilege level). Use when you need to determine which workspaces a user can access and their permission level in each. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string to filter results by workspace slug or permission level using Bitbucket's filtering syntax. Examples: q=workspace.slug="workspace1" or q=permission="owner". Supported fields: workspace.slug (workspace identifier), permission (permission level). Use exact match with = operator. String values must be enclosed in double quotes. | | `page` | integer | No | Page number for pagination. Use this to navigate through multiple pages of results. | | `pagelen` | integer | No | Number of items per page for pagination. Controls how many workspace permission objects are returned in a single response. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user workspaces **Slug:** `BITBUCKET_GET_USER_WORKSPACES` Tool to retrieve all workspaces accessible to the authenticated user. Use when you need to list workspaces the current user can access, optionally filtered by workspace slug or permission level. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string to filter workspaces by attributes such as workspace slug or permission level. Examples: 'workspace.slug="my-workspace"' or 'permission="owner"'. Follow Bitbucket's filtering syntax for complex queries. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get workspace **Slug:** `BITBUCKET_GET_WORKSPACE` Retrieves detailed information about a specific Bitbucket workspace. Use when you need to get workspace metadata, settings, or details. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workspace` | string | Yes | The workspace ID (slug) or workspace UUID surrounded by curly-braces. Example: 'my-workspace' or '{workspace-uuid}'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Workspace Pull Requests by User **Slug:** `BITBUCKET_GET_WORKSPACES_PULLREQUESTS` Tool to get all workspace pull requests authored by a specified user. Use when you need to retrieve pull requests created by a specific user across all repositories in a workspace. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `state` | string ("OPEN" | "MERGED" | "DECLINED") | No | Lifecycle state of a pull request. | | `pagelen` | integer | No | Number of pull requests per page (1-100). Bitbucket default is 10 if not specified. | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `selected_user` | string | Yes | The username of the user whose pull requests you want to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search code in workspace **Slug:** `BITBUCKET_GET_WORKSPACES_SEARCH_CODE` Tool to search for code in the repositories of the specified workspace. Use when you need to find specific code patterns, function definitions, or text across all repositories in a workspace. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for pagination. Use this to navigate through multiple pages of search results. | | `fields` | string | No | Additional fields to include in the response, using the fields parameter syntax. For example, '+values.file.commit.repository' to include repository details for each code match. | | `pagelen` | integer | No | Number of results per page. Controls how many code search results are returned in a single response. | | `workspace` | string | Yes | The workspace identifier. This can be the workspace slug (e.g., 'my-workspace') or its UUID enclosed in curly braces (e.g., '{workspace-uuid}'). | | `search_query` | string | Yes | The search query string to search for in the code. Can use advanced syntax like 'foo+repo:demo' to search within specific repositories, or 'test+ext:py' to filter by file extension. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List branches **Slug:** `BITBUCKET_LIST_BRANCHES` Lists branches in a Bitbucket repository with optional server-side filtering by name pattern (BBQL) and sorting. Use when you need to discover available branches, search for specific branch patterns, or navigate repository branch structure. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string using Bitbucket Query Language (BBQL) to filter branches. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal). String values MUST be enclosed in double quotes. Common use case: filter by branch name pattern using 'name~"pattern"'. Examples: 'name~"feature/"' (branches starting with feature/), 'name="main"' (exact match for main branch). Combine multiple conditions with AND/OR (e.g., 'name~"feature/" OR name~"bugfix/"'). | | `page` | integer | No | Page number for paginated results (starts from 1). | | `sort` | string | No | Field for sorting branch results. Prefix with '-' for descending order. Common sortable fields: 'name', 'target.date' (commit date). Default sorting applies natural sorting for branch names with numeric values. | | `pagelen` | integer | No | Number of branches per page (1-100). Bitbucket default is typically 10 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List commits **Slug:** `BITBUCKET_LIST_COMMITS` Tool to retrieve a page of commits from a Bitbucket repository. Returns commits in reverse chronological order (newest first), similar to git log. Use when you need to browse commit history, filter commits by branch/tag, or restrict to commits affecting a specific path. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `path` | string | No | Filter commits to only those that affect the specified file or directory path. | | `exclude` | string | No | Branch or tag name, or commit SHA to exclude from the commit history. Commits reachable from this ref will be excluded. Multiple values can be separated by commas. | | `include` | string | No | Branch or tag name, or commit SHA to include in the commit history. If not specified, the repository's default branch is used. Multiple values can be separated by commas (e.g., 'main,develop'). | | `pagelen` | integer | No | Number of commits per page (1-100). Bitbucket default is typically 30 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List commits from revision **Slug:** `BITBUCKET_LIST_COMMITS_FROM_REVISION` Tool to list commits starting from a specific revision in a Bitbucket repository. Commits are paginated and returned in reverse chronological order. Use when you need to retrieve commit history from a specific commit, branch, or tag. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `path` | string | No | Optional file path to filter commits. Only commits that modified this file or directory will be returned. | | `exclude` | string | No | Optional commit hash or branch to exclude from the results. Can be used to create a range with the 'include' parameter. | | `include` | string | No | Optional commit hash or branch to include in the results. Can be used to create a range with the 'exclude' parameter. | | `pagelen` | integer | No | Number of commits per page (1-100). Bitbucket default is typically 30 if not specified. | | `revision` | string | Yes | The commit hash, branch name, tag, or other revision identifier to start listing commits from. Commits are returned in reverse chronological order starting from this revision. | | `repo_slug` | string | Yes | The slug of the repository. This is the repository's name, usually in lowercase and with hyphens instead of spaces. | | `workspace` | string | Yes | The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List commits on master **Slug:** `BITBUCKET_LIST_COMMITS_ON_MASTER` Lists commits on the master branch of a Bitbucket repository. Use when you need to retrieve the commit history for the master branch, including commit messages, authors, dates, and parent relationships. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of commits per page (1-100). Bitbucket default is typically 30 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List deployments **Slug:** `BITBUCKET_LIST_DEPLOYMENTS` Lists deployments for a specified Bitbucket repository. Use when you need to view deployment history and status across environments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string for filtering deployment results using Bitbucket Query Language (BBQL). Use operators like '=' for exact match, '~' for contains, '!=' for not equal. | | `sort` | string | No | Field designation for sorting results. Prefix with '-' for descending order. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace ID or slug (URL-friendly name). This can be the workspace slug (e.g., 'my-workspace') or its UUID enclosed in curly braces (e.g., '{workspace-uuid}'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List issues in a repository **Slug:** `BITBUCKET_LIST_ISSUES` Lists issues in a Bitbucket repository with optional filtering by state, priority, kind, or assignee. Use when you need to discover issue IDs or get an overview of repository issues. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `kind` | string | No | Filter issues by kind (type). Use 'bug', 'enhancement', 'proposal', or 'task'. If not provided, issues of all kinds are returned. | | `page` | integer | No | Page number for paginated results (starts from 1). | | `state` | string | No | Filter issues by state. Use a specific state like 'new', 'open', 'resolved', 'on hold', 'invalid', 'duplicate', 'wontfix', or 'closed'. If not provided, all issues regardless of state are returned. | | `pagelen` | integer | No | Number of issues per page (1-100). Bitbucket default is 10 if not specified. | | `assignee` | string | No | Filter issues by assignee. Provide the Bitbucket account ID (UUID) of the assignee. Use 'null' (as a string) to find unassigned issues. If not provided, issues with any assignee (or no assignee) are returned. | | `priority` | string | No | Filter issues by priority. Use 'trivial', 'minor', 'major', 'critical', or 'blocker'. If not provided, issues of all priorities are returned. | | `repo_slug` | string | Yes | The slug (URL-friendly name) of the repository. | | `workspace` | string | Yes | The workspace ID or slug (URL-friendly name) that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List pipelines **Slug:** `BITBUCKET_LIST_PIPELINES` Tool to find pipelines in a Bitbucket repository. Returns pipeline metadata including state, trigger, and duration. Use when you need to browse pipeline history or check pipeline status. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of pipelines per page (1-100). Bitbucket default is typically 10 if not specified. | | `repo_slug` | string | Yes | The repository slug (URL-friendly identifier). | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List pull requests **Slug:** `BITBUCKET_LIST_PULL_REQUESTS` Lists pull requests in a specified, accessible Bitbucket repository, optionally filtering by state (OPEN, MERGED, DECLINED). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `state` | string ("OPEN" | "MERGED" | "DECLINED") | No | Lifecycle state of a pull request. | | `pagelen` | integer | No | Number of pull requests per page (1-50). Bitbucket default is 10 if not specified. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List pull request tasks **Slug:** `BITBUCKET_LIST_PULL_REQUEST_TASKS` Lists all tasks associated with a pull request in a Bitbucket repository. Use when you need to view or track tasks on a PR. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Page number for paginated results (starts from 1). | | `pagelen` | integer | No | Number of tasks per page (1-100). Bitbucket default is 10 if not specified. | | `repo_slug` | string | Yes | The slug (URL-friendly name) of the repository. | | `workspace` | string | Yes | The workspace ID or slug (URL-friendly name) that owns the repository. | | `pull_request_id` | integer | Yes | The unique identifier of the pull request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List all public repositories **Slug:** `BITBUCKET_LIST_REPOSITORIES` Retrieves a paginated list of all public repositories on Bitbucket. Use when you need to discover or search across public repositories, optionally filtered by role, query string, creation date, or sorted by various fields. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string using Bitbucket Query Language (BBQL) to filter repositories. Note: This parameter requires the 'role' parameter to be specified. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal), '>' '>=' '<' '<=' (comparison for dates/numbers). String values MUST be enclosed in double quotes. Valid repository fields: 'name', 'full_name', 'is_private', 'created_on', 'updated_on', 'language'. Combine multiple conditions with AND/OR (e.g., 'name~"api" AND is_private=false'). | | `role` | string ("member" | "contributor" | "admin" | "owner") | No | Enum for repository role filter values. | | `sort` | string | No | Field to sort returned repositories by. Prefix with a hyphen (-) for descending order. Common sortable fields: 'name', 'created_on', 'updated_on'. | | `after` | string | No | ISO-8601 timestamp to filter results created after this date/time. Format: YYYY-MM-DDTHH:mm:ss.sssZ (e.g., '2024-01-01T00:00:00.000Z'). Only repositories created after this timestamp will be returned. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List repository environments **Slug:** `BITBUCKET_LIST_REPOSITORIES_ENVIRONMENTS` List all deployment environments configured for a Bitbucket repository. Use when you need to view available environments for deployments, check environment configurations, or select an environment for deployment operations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string for filtering environment results using Bitbucket Query Language (BBQL). Use operators like '=' for exact match, '~' for contains, '!=' for not equal. | | `sort` | string | No | Field designation for sorting results. Prefix with '-' for descending order. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) or UUID. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be the workspace slug (e.g., 'my-workspace') or its UUID enclosed in curly braces (e.g., '{workspace-uuid}'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List repositories in workspace **Slug:** `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` Lists repositories in a specified Bitbucket workspace, accessible to the authenticated user, with options to filter by role or query string, and sort results. Responses are paginated; iterate using the `next` field in each response until it is absent to retrieve all repositories. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string using Bitbucket Query Language (BBQL) to filter repositories. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal), '>' '>=' '<' '<=' (comparison for dates/numbers). String values MUST be enclosed in double quotes. Valid repository fields: 'name', 'full_name', 'project.key', 'is_private', 'created_on', 'updated_on', 'language'. Combine multiple conditions with AND/OR (e.g., 'name~"api" AND is_private=true'). Note: 'repository' is NOT a valid field name - use 'name' instead. Invalid or malformed expressions return empty results silently rather than an error. | | `role` | string | No | Filters repositories by the authenticated user's role within each repository. | | `sort` | string | No | Field for sorting repository results. Prefix with '-' for descending order. Common sortable fields: 'name', 'updated_on', 'created_on'. | | `workspace` | string | Yes | The identifier of the Bitbucket workspace. This can be the workspace slug (e.g., 'my-workspace') or its UUID enclosed in curly braces (e.g., '{workspace-uuid}'). Empty results may indicate insufficient permissions rather than an invalid identifier. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List repository paths **Slug:** `BITBUCKET_LIST_REPOSITORY_PATHS` Lists file and directory entries under a repository path at a given revision, with optional breadth-first recursion via max_depth for repository traversal and scanning. Fails if the path points to a file rather than a directory. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Filter query string using Bitbucket's REST API filtering syntax to narrow results. | | `page` | integer | No | Page number for paginated results (starts from 1). | | `path` | string | No | Directory path within the repository to list. Use empty string for root. Must be a directory, not a file. | | `sort` | string | No | Field name for sorting results. Prefix with '-' for descending order. | | `commit` | string | Yes | Commit hash, branch name, or tag to list paths from. Determines the revision to traverse. | | `pagelen` | integer | No | Number of entries per page (1-100). Controls pagination size. | | `max_depth` | integer | No | Maximum depth for breadth-first recursive directory traversal. If specified, includes nested subdirectories up to this depth. | | `repo_slug` | string | Yes | Repository slug or UUID (typically URL-formatted name). | | `workspace` | string | Yes | Workspace ID or UUID (often username or team name) containing the repository. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List snippets **Slug:** `BITBUCKET_LIST_SNIPPETS` Returns all snippets accessible to the authenticated user. Use when you need to discover or list snippets, optionally filtered by role (owner, contributor, or member). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `role` | string ("owner" | "contributor" | "member") | No | Enum for snippet role filter values. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List tags **Slug:** `BITBUCKET_LIST_TAGS` Lists tags in a Bitbucket repository with optional server-side filtering by name pattern or commit hash (BBQL) and sorting. Use when you need to discover available tags, search for specific tag patterns, or find tags pointing to specific commits. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string using Bitbucket Query Language (BBQL) to filter tags. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal). String values MUST be enclosed in double quotes. Common use case: filter by tag name pattern using 'name~"pattern"' or by commit hash using 'target.hash="hash"'. Examples: 'name~"v1."' (tags starting with v1.), 'name="v1.0.0"' (exact match for v1.0.0 tag), 'target.hash="a1b2c3d4"' (tags pointing to specific commit). Combine multiple conditions with AND/OR (e.g., 'name~"v1." OR name~"v2."'). | | `page` | integer | No | Page number for paginated results (starts from 1). | | `sort` | string | No | Field for sorting tag results. Prefix with '-' for descending order. Common sortable fields: 'name', 'target.date' (commit date). Default sorting applies natural sorting for tag names with numeric values. | | `pagelen` | integer | No | Number of tags per page (1-100). Bitbucket default is typically 10 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List versions **Slug:** `BITBUCKET_LIST_VERSIONS` Lists versions (milestones) in a Bitbucket repository's issue tracker. Use when you need to discover available versions for associating with issues, or to retrieve version IDs for use with create_issue. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string using Bitbucket Query Language (BBQL) to filter versions. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal). String values MUST be enclosed in double quotes. Common use case: filter by version name pattern using 'name~"pattern"'. Examples: 'name~"1."' (versions starting with 1.), 'name="2.0"' (exact match for version 2.0). | | `page` | integer | No | Page number for paginated results (starts from 1). | | `sort` | string | No | Field for sorting version results. Prefix with '-' for descending order. Common sortable fields: 'name'. Default sorting applies natural sorting. | | `pagelen` | integer | No | Number of versions per page (1-100). Bitbucket default is typically 10 if not specified. | | `repo_slug` | string | Yes | The slug or UUID of the repository. This is usually the repository's name in URL-friendly format. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List workspace members **Slug:** `BITBUCKET_LIST_WORKSPACE_MEMBERS` Lists all members of a specified Bitbucket workspace; the workspace must exist. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workspace` | string | Yes | The workspace ID (UUID) or slug from which to list members. The slug is the user-friendly, URL-safe identifier for the workspace. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List workspace projects **Slug:** `BITBUCKET_LIST_WORKSPACE_PROJECTS` Lists projects in a specified Bitbucket workspace. Use when you need to retrieve all projects belonging to a workspace. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string to filter projects by attributes, following Bitbucket's filtering syntax. Syntax: 'field operator value'. Operators: '=' (exact match), '~' (contains substring), '!=' (not equal). String values MUST be enclosed in double quotes. Valid project fields: 'name', 'key', 'is_private'. Combine multiple conditions with AND/OR (e.g., 'name~"api" AND is_private=true'). | | `page` | integer | No | Specifies which page of results to return. Page numbering starts at 1. | | `sort` | string | No | Field to sort returned projects by; prefix with a hyphen (-) for descending order. Common sortable fields: 'name', 'key', 'created_on', 'updated_on'. | | `pagelen` | integer | No | Controls the number of items per page. Must be between 1 and 100. | | `workspace` | string | Yes | The identifier of the Bitbucket workspace. This can be the workspace slug (e.g., 'my-workspace') or its UUID enclosed in curly braces (e.g., '{workspace-uuid}'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List workspaces **Slug:** `BITBUCKET_LIST_WORKSPACES` Lists Bitbucket workspaces accessible to the authenticated user, optionally filtered and sorted. Results are paginated; follow the `next` field in each response to retrieve subsequent pages until `next` is absent. When multiple workspaces are returned, verify the correct `slug` or UUID before passing to downstream tools. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Query string to filter workspaces by attributes, following Bitbucket's filtering syntax. | | `sort` | string | No | Field to sort returned workspaces by; prefix with a hyphen (-) for descending order. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Merge Pull Request **Slug:** `BITBUCKET_MERGE_PULL_REQUEST` Tool to merge a Bitbucket Cloud pull request via the REST API. Use when you need to complete a PR merge after approval and checks pass. Supports custom merge messages, merge strategies, and source branch deletion. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `message` | string | No | Custom merge commit message. If not provided, Bitbucket generates a default message. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `merge_strategy` | string | No | Merge strategy to use. Common values include 'merge_commit', 'squash', 'fast_forward'. If not specified, uses the repository's default merge strategy. | | `pull_request_id` | integer | Yes | The ID of the pull request to merge. | | `close_source_branch` | boolean | No | Whether to close the source branch after merging. If not specified, uses the repository's default setting. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Request Pull Request Changes **Slug:** `BITBUCKET_REQUEST_PULL_REQUEST_CHANGES` Tool to request changes on a pull request as the authenticated user. Use when you need to formally request changes in a pull request review process, indicating the PR needs modifications before approval. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo_slug` | string | Yes | Repository slug (URL-friendly name). | | `workspace` | string | Yes | Workspace ID or slug (URL-friendly name). | | `pull_request_id` | integer | Yes | The ID of the pull request to request changes on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Resolve pull request comment **Slug:** `BITBUCKET_RESOLVE_PULL_REQUEST_COMMENT` Tool to resolve or reopen a pull request comment thread. Use when marking a comment as addressed during review or reopening a previously resolved thread. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `action` | string ("resolve" | "reopen") | No | Action to perform: 'resolve' marks the comment thread as addressed, 'reopen' unmarks it. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. | | `comment_id` | integer | Yes | The unique identifier for the comment to resolve or reopen. | | `pull_request_id` | integer | Yes | The unique identifier of the pull request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search code in team repositories **Slug:** `BITBUCKET_SEARCH_TEAM_CODE` Search for code in repositories of a specified team. Matches can occur in file content or paths. Note: Teams endpoints were deprecated in Oct 2020; use workspace search endpoints for new integrations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Which page of search results to retrieve (starts from 1). | | `pagelen` | integer | No | How many search results to retrieve per page (1-100). Default is 10 if not specified. | | `username` | string | Yes | The team account username or UUID in curly braces (e.g., 'team-name' or '{team-uuid}'). Note: Teams endpoints are deprecated since Oct 2020; consider using workspace endpoints instead. | | `search_query` | string | Yes | The search query string. Supports advanced syntax like 'repo:demo' to filter by repository, or combine terms with AND/OR operators. Same syntax as the Bitbucket UI search. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search code in user repositories **Slug:** `BITBUCKET_SEARCH_USER_REPOSITORIES_CODE` Tool to search for code in the repositories of a specified user. Use when you need to find specific code patterns, functions, or text across all repositories owned by a user. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `page` | integer | No | Which page of search results to retrieve (default: 1). | | `fields` | string | No | Request additional fields in the response. Use '+' prefix to expand nested fields (e.g., '+values.file.commit.repository' to include repository details). | | `pagelen` | integer | No | How many search results per page (default: 10). | | `search_query` | string | Yes | The search query using the same syntax as the Bitbucket UI. Can include repo filters (e.g., 'test', 'foo+repo:demo'). | | `selected_user` | string | Yes | The username of the user whose repositories to search. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update commit insight report **Slug:** `BITBUCKET_UPDATE_INSIGHTS_PROJECTS_REPOS_COMMITS_REPORTS` Create or update an insight report for a commit. Creates a new report if it doesn't exist, or replaces the existing one if a report already exists for the given repository, commit, and report key. Note: replacing an existing report will be rejected if the authenticated user was not the creator of the specified report. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | array | No | Array of data items containing additional information about the report. Maximum 6 items. | | `link` | string | No | An external link providing more information about the report. Must be a valid HTTP/HTTPS URL. | | `title` | string | Yes | The title of the report. Maximum 450 characters. | | `commit` | string | Yes | The commit hash to which the report belongs. This is the full SHA-1 commit identifier (40 characters). | | `result` | string ("PASSED" | "FAILED" | "PENDING") | No | Enum for report results. | | `details` | string | Yes | Detailed description of the report. Maximum 2000 characters. Supports escaped newlines. | | `logo_url` | string | No | URL to the logo image for the reporting tool. Must be a valid HTTP/HTTPS URL. | | `reportId` | string | Yes | Unique identifier for the report. Recommend using reverse DNS namespacing (e.g., 'com.company.tool.report-name'). | | `reporter` | string | No | The name of the system or tool that created the report. Maximum 450 characters. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) that contains the commit. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | | `report_type` | string ("SECURITY" | "COVERAGE" | "TEST" | "BUG") | Yes | The type of report: SECURITY, COVERAGE, TEST, or BUG. | | `remote_link_enabled` | boolean | No | Whether remote link is enabled for the report. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update an issue **Slug:** `BITBUCKET_UPDATE_ISSUE` Updates an existing issue in a Bitbucket repository by modifying specified attributes; requires `workspace`, `repo_slug`, `issue_id`, and at least one attribute to update. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `kind` | string ("bug" | "enhancement" | "proposal" | "task") | No | Types/kinds of Bitbucket issues. | | `state` | string ("new" | "open" | "resolved" | "on hold" | "invalid" | "duplicate" | "wontfix" | "closed") | No | States for Bitbucket issues. | | `title` | string | No | The new title for the issue. If omitted, the title remains unchanged. | | `content` | string | No | The new content or description for the issue, in raw text format. If omitted, the content remains unchanged. | | `version` | string | No | The name of the version affected by this issue (e.g., '1.0.0', '2.0-beta'). If omitted, the version remains unchanged. | | `issue_id` | string | Yes | The unique identifier (ID) of the issue to be updated. | | `priority` | string ("trivial" | "minor" | "major" | "critical" | "blocker") | No | Priority levels for Bitbucket issues. | | `component` | string | No | The name of the component to associate with the issue (e.g., 'API', 'Frontend'). If omitted, the component remains unchanged. | | `milestone` | string | No | The name of the milestone to associate with the issue (e.g., 'Sprint 1', 'v1.0 Launch'). If omitted, the milestone remains unchanged. | | `repo_slug` | string | Yes | The slug or name of the repository (e.g., 'my-app-repo'). | | `workspace` | string | Yes | The workspace ID or slug that owns the repository (e.g., 'my-company' or '{123e4567-e89b-12d3-a456-426614174000}'). | | `assignee_account_id` | string | No | The Bitbucket account ID (UUID) of the user to assign the issue to. If omitted, the assignee remains unchanged. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Pull Request **Slug:** `BITBUCKET_UPDATE_PULL_REQUEST` Tool to update an existing pull request's editable fields (e.g., title, description, reviewers) via the Bitbucket Cloud API. Use when you need to modify a pull request without creating a new one. Only sends fields that are explicitly provided to avoid accidental overwrites. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `draft` | boolean | No | If true, marks the pull request as a draft. If false, marks it as ready for review. If omitted, draft status remains unchanged. | | `title` | string | No | Updated title for the pull request. If omitted, title remains unchanged. | | `repo_slug` | string | Yes | Repository slug (URL-friendly name) or UUID. | | `reviewers` | array | No | Updated list of Bitbucket user UUIDs to be reviewers. Replaces existing reviewers. If omitted, reviewers remain unchanged. | | `workspace` | string | Yes | Workspace ID (slug) or workspace UUID that owns the repository. | | `description` | string | No | Updated Markdown description for the pull request. If omitted, description remains unchanged. | | `pull_request_id` | integer | Yes | Unique ID of the pull request to update. | | `close_source_branch` | boolean | No | If true, automatically closes the source branch upon pull request merge. If omitted, setting remains unchanged. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update commit comment **Slug:** `BITBUCKET_UPDATE_REPOSITORIES_COMMIT_COMMENTS` Updates the contents of a comment on a commit. Use when you need to modify an existing comment's text on a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commit` | string | Yes | The commit hash to update the comment on. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name). | | `workspace` | string | Yes | The workspace slug or UUID that owns the repository. | | `comment_id` | string | Yes | The unique identifier for the comment to update. | | `content_raw` | string | Yes | The updated raw text content for the comment. Supports markdown formatting. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update commit report annotation **Slug:** `BITBUCKET_UPDATE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONS` Creates or updates an individual annotation for a commit report. Use when you need to add or modify code analysis findings (vulnerabilities, code smells, or bugs) identified in a commit. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `line` | integer | No | Line number in the file where the finding occurs. Must be a positive integer. | | `link` | string | No | URL providing more information about the finding, such as documentation or issue tracker link. | | `path` | string | No | File path where the annotation applies, relative to the repository root. | | `commit` | string | Yes | The commit hash to which the report belongs. This is the full SHA-1 commit identifier. | | `result` | string ("PASSED" | "FAILED" | "IGNORED" | "SKIPPED") | No | Enumeration of annotation result statuses. | | `details` | string | No | Extended description providing additional context, remediation guidance, or technical details about the finding. | | `summary` | string | Yes | Brief description of the finding. Should concisely explain what was detected. | | `reportId` | string | Yes | Either the uuid or external-id of the report that will contain the annotation. | | `severity` | string ("CRITICAL" | "HIGH" | "MEDIUM" | "LOW") | Yes | Impact level of the finding. CRITICAL for severe issues requiring immediate attention, HIGH for important issues, MEDIUM for moderate concerns, LOW for minor issues. | | `repo_slug` | string | Yes | The repository slug (URL-friendly name) that contains the commit. | | `workspace` | string | Yes | The workspace ID or slug that owns the repository. This can be a user's username or a team's slug. | | `external_id` | string | No | Unique identifier for tracking this annotation in an external system. Useful for correlating with external tools. | | `annotationId` | string | Yes | Either the uuid or external-id of the annotation to create or update. | | `annotation_type` | string ("VULNERABILITY" | "CODE_SMELL" | "BUG") | Yes | Type of annotation indicating the nature of the finding: VULNERABILITY for security issues, CODE_SMELL for maintainability issues, or BUG for functional defects. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update team pipeline variable **Slug:** `BITBUCKET_UPDATE_TEAMS_PIPELINES_CONFIG_VARIABLES` Updates a team-level pipeline configuration variable in Bitbucket. Use when you need to modify existing environment variables or configuration values that are available to all pipelines within a team. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The name/key of the pipeline variable. Must be unique within the team's pipeline configuration. | | `value` | string | Yes | The updated value of the pipeline variable. This will be available to all pipelines in the team. | | `secured` | boolean | No | Whether the variable should be secured (masked in logs). Set to `True` for sensitive values like passwords or API keys, `False` for non-sensitive values. | | `username` | string | Yes | The team username that owns the pipeline configuration. This is the team identifier in Bitbucket. | | `variable_uuid` | string | Yes | The UUID of the pipeline variable to update. This must be in UUID format (e.g., 252a372b-3e5d-4869-9df5-c379d6b062e9) and can be optionally wrapped in curly braces. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update user pipeline variable **Slug:** `BITBUCKET_UPDATE_USERS_PIPELINES_CONFIG_VARIABLES` Updates a user-level pipeline variable for Bitbucket pipelines. Use when you need to modify account-level configuration variables such as changing the value, key name, or security status. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | No | The updated name/key of the pipeline variable. If omitted, the key remains unchanged. | | `value` | string | No | The updated value of the pipeline variable. If omitted, the value remains unchanged. | | `secured` | boolean | No | Whether the variable should be secured/encrypted (true) or stored as plain text (false). If omitted, the secured status remains unchanged. | | `selected_user` | string | Yes | The UUID or username of the user. When using UUID format, it should be URL-encoded (e.g., %7B4f3ecac3-c951-41d4-8a4c-95f40be978fc%7D for {4f3ecac3-c951-41d4-8a4c-95f40be978fc}). | | `variable_uuid` | string | Yes | The UUID of the pipeline variable to update. This can be obtained from the list or get variable endpoints. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not |