bitbucket-automation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Bitbucket Automation via Rube MCP

基于Rube MCP的Bitbucket自动化

Automate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.

通过Composio的Bitbucket工具包，实现Bitbucket操作的自动化，包括仓库管理、拉取请求工作流、分支操作、问题追踪以及工作区管理。

Prerequisites

前提条件

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Bitbucket connection via
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
bitbucket
```
Always call
```
RUBE_SEARCH_TOOLS
```
first to get current tool schemas

必须已连接Rube MCP（需提供RUBE_SEARCH_TOOLS）
通过
```
RUBE_MANAGE_CONNECTIONS
```
并使用
```
bitbucket
```
工具包，建立有效的Bitbucket连接
请始终先调用
```
RUBE_SEARCH_TOOLS
```
以获取最新的工具架构

Setup

设置步骤

Get Rube MCP: Add

https://rube.app/mcp

as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming
```
RUBE_SEARCH_TOOLS
```
responds
Call
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
bitbucket
```
If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth
Confirm connection status shows ACTIVE before running any workflows

获取Rube MCP：在客户端配置中添加

https://rube.app/mcp

作为MCP服务器。无需API密钥 —— 只需添加该端点即可使用。

确认
```
RUBE_SEARCH_TOOLS
```
可正常响应，以此验证Rube MCP是否可用
调用
```
RUBE_MANAGE_CONNECTIONS
```
并指定工具包为
```
bitbucket
```
如果连接状态未激活，请按照返回的授权链接完成Bitbucket OAuth认证
在运行任何工作流之前，确认连接状态显示为已激活

Core Workflows

核心工作流

1. Manage Pull Requests

1. 管理拉取请求

When to use: User wants to create, review, or inspect pull requests

Tool sequence:

```
BITBUCKET_LIST_WORKSPACES
```
- Discover accessible workspaces [Prerequisite]
```
BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE
```
- Find the target repository [Prerequisite]
```
BITBUCKET_LIST_BRANCHES
```
- Verify source and destination branches exist [Prerequisite]
```
BITBUCKET_CREATE_PULL_REQUEST
```
- Create a new PR with title, source branch, and optional reviewers [Required]
```
BITBUCKET_LIST_PULL_REQUESTS
```
- List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]
```
BITBUCKET_GET_PULL_REQUEST
```
- Get full details of a specific PR by ID [Optional]
```
BITBUCKET_GET_PULL_REQUEST_DIFF
```
- Fetch unified diff for code review [Optional]
```
BITBUCKET_GET_PULL_REQUEST_DIFFSTAT
```
- Get changed files with lines added/removed [Optional]

Key parameters:

```
workspace
```
: Workspace slug or UUID (required for all operations)
```
repo_slug
```
: URL-friendly repository name
```
source_branch
```
: Branch with changes to merge
```
destination_branch
```
: Target branch (defaults to repo main branch if omitted)
```
reviewers
```
: List of objects with
```
uuid
```
field for reviewer assignment
```
state
```
: Filter for LIST_PULL_REQUESTS -
```
OPEN
```
,
```
MERGED
```
, or
```
DECLINED
```
```
max_chars
```
: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs

Pitfalls:

```
reviewers
```
expects an array of objects with
```
uuid
```
key, NOT usernames:
```
[{"uuid": "{...}"}]
```
UUID format must include curly braces:
```
{123e4567-e89b-12d3-a456-426614174000}
```
```
destination_branch
```
defaults to the repo's main branch if omitted, which may not be
```
main
```
```
pull_request_id
```
is an integer for GET/DIFF operations but comes back as part of PR listing
Large diffs can overwhelm context; always set
```
max_chars
```
(e.g., 50000) on GET_PULL_REQUEST_DIFF

适用场景：用户需要创建、评审或查看拉取请求

工具执行序列:

```
BITBUCKET_LIST_WORKSPACES
```
- 查看可访问的工作区 [前置条件]

BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE

- 找到目标仓库 [前置条件]

```
BITBUCKET_LIST_BRANCHES
```
- 验证源分支和目标分支是否存在 [前置条件]
```
BITBUCKET_CREATE_PULL_REQUEST
```
- 创建新的PR，需指定标题、源分支，可选择添加评审人 [必填步骤]
```
BITBUCKET_LIST_PULL_REQUESTS
```
- 按状态（OPEN、MERGED、DECLINED）筛选列出PR [可选步骤]
```
BITBUCKET_GET_PULL_REQUEST
```
- 通过ID获取特定PR的完整详情 [可选步骤]
```
BITBUCKET_GET_PULL_REQUEST_DIFF
```
- 获取统一差异对比用于代码评审 [可选步骤]
```
BITBUCKET_GET_PULL_REQUEST_DIFFSTAT
```
- 获取变更文件及增删行数统计 [可选步骤]

关键参数:

```
workspace
```
: 工作区别名或UUID（所有操作必填）
```
repo_slug
```
: 符合URL规范的仓库名称
```
source_branch
```
: 包含待合并变更的分支
```
destination_branch
```
: 目标分支（若省略则默认使用仓库的主分支）
```
reviewers
```
: 包含
```
uuid
```
字段的对象列表，用于指定评审人

state

: 用于

LIST_PULL_REQUESTS

的筛选条件 -

OPEN

、

MERGED

或

DECLINED

```
max_chars
```
:
```
GET_PULL_REQUEST_DIFF
```
的截断限制，用于处理大型差异对比内容

注意事项:

```
reviewers
```
参数要求传入包含
```
uuid
```
键的对象数组，而非用户名：
```
[{"uuid": "{...}"}]
```
UUID格式必须包含大括号：
```
{123e4567-e89b-12d3-a456-426614174000}
```
若省略
```
destination_branch
```
，默认使用仓库的主分支，但该分支名称可能不是
```
main
```
```
pull_request_id
```
在GET/DIFF操作中为整数，但会作为PR列表的返回字段
大型差异对比内容可能超出上下文限制；请始终为
```
GET_PULL_REQUEST_DIFF
```
设置
```
max_chars
```
（例如50000）

2. Manage Repositories and Workspaces

2. 管理仓库与工作区

When to use: User wants to list, create, or delete repositories or explore workspaces

Tool sequence:

```
BITBUCKET_LIST_WORKSPACES
```
- List all accessible workspaces [Required]
```
BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE
```
- List repos with optional BBQL filtering [Required]
```
BITBUCKET_CREATE_REPOSITORY
```
- Create a new repo with language, privacy, and project settings [Optional]
```
BITBUCKET_DELETE_REPOSITORY
```
- Permanently delete a repository (irreversible) [Optional]
```
BITBUCKET_LIST_WORKSPACE_MEMBERS
```
- List members for reviewer assignment or access checks [Optional]

Key parameters:

```
workspace
```
: Workspace slug (find via LIST_WORKSPACES)
```
repo_slug
```
: URL-friendly name for create/delete

: BBQL query filter (e.g.,

name~"api"

project.key="PROJ"

is_private=true

)

```
role
```
: Filter repos by user role:
```
member
```
,
```
contributor
```
,
```
admin
```
,
```
owner
```
```
sort
```
: Sort field with optional
```
-
```
prefix for descending (e.g.,
```
-updated_on
```
)
```
is_private
```
: Boolean for repository visibility (defaults to
```
true
```
)
```
project_key
```
: Bitbucket project key; omit to use workspace's oldest project

Pitfalls:

```
BITBUCKET_DELETE_REPOSITORY
```
is irreversible and does not affect forks
BBQL string values MUST be enclosed in double quotes:
```
name~"my-repo"
```
not
```
name~my-repo
```
```
repository
```
is NOT a valid BBQL field; use
```
name
```
instead
Default pagination is 10 results; set
```
pagelen
```
explicitly for complete listings
```
CREATE_REPOSITORY
```
defaults to private; set
```
is_private: false
```
for public repos

适用场景：用户需要列出、创建或删除仓库，或查看工作区信息

工具执行序列:

```
BITBUCKET_LIST_WORKSPACES
```
- 列出所有可访问的工作区 [必填步骤]
```
BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE
```
- 列出仓库，可通过BBQL筛选 [必填步骤]
```
BITBUCKET_CREATE_REPOSITORY
```
- 创建新仓库，可设置语言、隐私性及项目配置 [可选步骤]
```
BITBUCKET_DELETE_REPOSITORY
```
- 永久删除仓库（不可恢复） [可选步骤]
```
BITBUCKET_LIST_WORKSPACE_MEMBERS
```
- 列出工作区成员，用于指定评审人或权限检查 [可选步骤]

关键参数:

```
workspace
```
: 工作区别名（可通过
```
LIST_WORKSPACES
```
获取）
```
repo_slug
```
: 用于创建/删除操作的符合URL规范的仓库名称

: BBQL查询筛选条件（例如

name~"api"

project.key="PROJ"

is_private=true

）

```
role
```
: 按用户角色筛选仓库：
```
member
```
、
```
contributor
```
、
```
admin
```
、
```
owner
```
```
sort
```
: 排序字段，可添加
```
-
```
前缀表示降序（例如
```
-updated_on
```
）
```
is_private
```
: 仓库可见性的布尔值（默认值为
```
true
```
）
```
project_key
```
: Bitbucket项目密钥；若省略则使用工作区中创建时间最早的项目

注意事项:

```
BITBUCKET_DELETE_REPOSITORY
```
操作不可恢复，且不会影响派生仓库
BBQL的字符串值必须用双引号包裹：
```
name~"my-repo"
```
而非
```
name~my-repo
```
```
repository
```
不是有效的BBQL字段；请使用
```
name
```
替代
默认分页为10条结果；如需完整列表请显式设置
```
pagelen
```
参数
```
CREATE_REPOSITORY
```
默认创建私有仓库；若需创建公开仓库请设置
```
is_private: false
```

3. Manage Issues

3. 管理问题

When to use: User wants to create, update, list, or comment on repository issues

Tool sequence:

```
BITBUCKET_LIST_ISSUES
```
- List issues with optional filters for state, priority, kind, assignee [Required]
```
BITBUCKET_CREATE_ISSUE
```
- Create a new issue with title, content, priority, and kind [Required]
```
BITBUCKET_UPDATE_ISSUE
```
- Modify issue attributes (state, priority, assignee, etc.) [Optional]
```
BITBUCKET_CREATE_ISSUE_COMMENT
```
- Add a markdown comment to an existing issue [Optional]
```
BITBUCKET_DELETE_ISSUE
```
- Permanently delete an issue [Optional]

Key parameters:

```
issue_id
```
: String identifier for the issue
```
title
```
,
```
content
```
: Required for creation
```
kind
```
:
```
bug
```
,
```
enhancement
```
,
```
proposal
```
, or
```
task
```

priority

trivial

minor

major

critical

, or

blocker

state

new

open

resolved

on hold

invalid

duplicate

wontfix

closed

```
assignee
```
: Bitbucket username for CREATE;
```
assignee_account_id
```
(UUID) for UPDATE
```
due_on
```
: ISO 8601 format date string

Pitfalls:

Issue tracker must be enabled on the repository (
```
has_issues: true
```
) or API calls will fail
```
CREATE_ISSUE
```
uses
```
assignee
```
(username string), but
```
UPDATE_ISSUE
```
uses
```
assignee_account_id
```
(UUID) -- they are different fields
```
DELETE_ISSUE
```
is permanent with no undo
```
state
```
values include spaces:
```
"on hold"
```
not
```
"on_hold"
```
Filtering by
```
assignee
```
in LIST_ISSUES uses account ID, not username; use
```
"null"
```
string for unassigned

适用场景：用户需要创建、更新、列出或评论仓库问题

工具执行序列:

```
BITBUCKET_LIST_ISSUES
```
- 列出问题，可按状态、优先级、类型、经办人筛选 [必填步骤]
```
BITBUCKET_CREATE_ISSUE
```
- 创建新问题，需指定标题、内容、优先级及类型 [必填步骤]
```
BITBUCKET_UPDATE_ISSUE
```
- 修改问题属性（状态、优先级、经办人等） [可选步骤]
```
BITBUCKET_CREATE_ISSUE_COMMENT
```
- 为现有问题添加Markdown格式的评论 [可选步骤]
```
BITBUCKET_DELETE_ISSUE
```
- 永久删除问题 [可选步骤]

关键参数:

```
issue_id
```
: 问题的字符串标识符
```
title
```
,
```
content
```
: 创建问题时必填
```
kind
```
: 问题类型：
```
bug
```
、
```
enhancement
```
、
```
proposal
```
或
```
task
```

priority

: 问题优先级：

trivial

、

minor

、

major

、

critical

或

blocker

state

: 问题状态：

new

、

open

、

resolved

、

on hold

、

invalid

、

duplicate

、

wontfix

、

closed

```
assignee
```
: 创建问题时使用的Bitbucket用户名；更新问题时使用
```
assignee_account_id
```
（UUID）
```
due_on
```
: ISO 8601格式的日期字符串

注意事项:

仓库必须已启用问题追踪功能（
```
has_issues: true
```
），否则API调用会失败
```
CREATE_ISSUE
```
使用
```
assignee
```
（字符串类型的用户名），但
```
UPDATE_ISSUE
```
使用
```
assignee_account_id
```
（UUID）—— 这是两个不同的参数
```
DELETE_ISSUE
```
操作永久生效，无法撤销
```
state
```
参数的部分值包含空格：
```
"on hold"
```
而非
```
"on_hold"
```
在
```
LIST_ISSUES
```
中按
```
assignee
```
筛选时需使用账户ID而非用户名；若要筛选未分配的问题，请使用字符串
```
"null"
```

4. Manage Branches

4. 管理分支

When to use: User wants to create branches or explore branch structure

Tool sequence:

```
BITBUCKET_LIST_BRANCHES
```
- List branches with optional BBQL filter and sorting [Required]
```
BITBUCKET_CREATE_BRANCH
```
- Create a new branch from a specific commit hash [Required]

Key parameters:

```
name
```
: Branch name without
```
refs/heads/
```
prefix (e.g.,
```
feature/new-login
```
)
```
target_hash
```
: Full SHA1 commit hash to branch from (must exist in repo)
```
q
```
: BBQL filter (e.g.,
```
name~"feature/"
```
,
```
name="main"
```
)
```
sort
```
: Sort by
```
name
```
or
```
-target.date
```
(descending commit date)
```
pagelen
```
: 1-100 results per page (default is 10)

Pitfalls:

```
CREATE_BRANCH
```
requires a full commit hash, NOT a branch name as
```
target_hash
```
Do NOT include
```
refs/heads/
```
prefix in branch names
Branch names must follow Bitbucket naming conventions (alphanumeric,
```
/
```
,
```
.
```
,
```
_
```
,
```
-
```
)
BBQL string values need double quotes:
```
name~"feature/"
```
not
```
name~feature/
```

适用场景：用户需要创建分支或查看分支结构

工具执行序列:

```
BITBUCKET_LIST_BRANCHES
```
- 列出分支，可通过BBQL筛选和排序 [必填步骤]
```
BITBUCKET_CREATE_BRANCH
```
- 基于特定提交哈希创建新分支 [必填步骤]

关键参数:

```
name
```
: 分支名称，无需添加
```
refs/heads/
```
前缀（例如
```
feature/new-login
```
）
```
target_hash
```
: 用于创建分支的完整SHA1提交哈希（必须存在于仓库中）
```
q
```
: BBQL筛选条件（例如
```
name~"feature/"
```
,
```
name="main"
```
）
```
sort
```
: 排序方式，可按
```
name
```
或
```
-target.date
```
（提交日期降序）
```
pagelen
```
: 每页显示1-100条结果（默认值为10）

注意事项:

```
CREATE_BRANCH
```
需要完整的提交哈希作为
```
target_hash
```
，而非分支名称
分支名称中请勿包含
```
refs/heads/
```
前缀
分支名称必须符合Bitbucket的命名规范（允许字母数字、
```
/
```
、
```
.
```
、
```
_
```
、
```
-
```
）
BBQL的字符串值需要用双引号包裹：
```
name~"feature/"
```
而非
```
name~feature/
```

5. Review Pull Requests with Comments

5. 为拉取请求添加评审评论

When to use: User wants to add review comments to pull requests, including inline code comments

Tool sequence:

```
BITBUCKET_GET_PULL_REQUEST
```
- Get PR details and verify it exists [Prerequisite]
```
BITBUCKET_GET_PULL_REQUEST_DIFF
```
- Review the actual code changes [Prerequisite]
```
BITBUCKET_GET_PULL_REQUEST_DIFFSTAT
```
- Get list of changed files [Optional]
```
BITBUCKET_CREATE_PULL_REQUEST_COMMENT
```
- Post review comments [Required]

Key parameters:

```
pull_request_id
```
: String ID of the PR
```
content_raw
```
: Markdown-formatted comment text
```
content_markup
```
: Defaults to
```
markdown
```
; also supports
```
plaintext
```
```
inline
```
: Object with
```
path
```
,
```
from
```
,
```
to
```
for inline code comments
```
parent_comment_id
```
: Integer ID for threaded replies to existing comments

Pitfalls:

```
pull_request_id
```
is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUEST
Inline comments require
```
inline.path
```
at minimum;
```
from
```
/
```
to
```
are optional line numbers
```
parent_comment_id
```
creates a threaded reply; omit for top-level comments
Line numbers in inline comments reference the diff, not the source file

适用场景：用户需要为拉取请求添加评审评论，包括代码行内评论

工具执行序列:

```
BITBUCKET_GET_PULL_REQUEST
```
- 获取PR详情并验证其存在 [前置条件]
```
BITBUCKET_GET_PULL_REQUEST_DIFF
```
- 查看实际代码变更 [前置条件]
```
BITBUCKET_GET_PULL_REQUEST_DIFFSTAT
```
- 获取变更文件列表 [可选步骤]
```
BITBUCKET_CREATE_PULL_REQUEST_COMMENT
```
- 发布评审评论 [必填步骤]

关键参数:

```
pull_request_id
```
: PR的字符串ID
```
content_raw
```
: Markdown格式的评论内容
```
content_markup
```
: 默认值为
```
markdown
```
；也支持
```
plaintext
```
```
inline
```
: 用于行内代码评论的对象，包含
```
path
```
、
```
from
```
、
```
to
```
字段
```
parent_comment_id
```
: 用于回复现有评论的整数ID，可创建线程化回复

注意事项:

在

CREATE_PULL_REQUEST_COMMENT

中

pull_request_id

是字符串，但在

GET_PULL_REQUEST

中是整数

行内评论至少需要
```
inline.path
```
参数；
```
from
```
/
```
to
```
为可选行号
```
parent_comment_id
```
用于创建线程化回复；若省略则创建顶级评论
行内评论中的行号引用的是差异对比内容中的行号，而非源文件中的行号

Common Patterns

通用模式

ID Resolution

ID解析

Always resolve human-readable names to IDs before operations:

Workspace:
```
BITBUCKET_LIST_WORKSPACES
```
to get workspace slugs

Repository:

BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE

with

filter to find repo slugs

Branch:
```
BITBUCKET_LIST_BRANCHES
```
to verify branch existence before PR creation
Members:
```
BITBUCKET_LIST_WORKSPACE_MEMBERS
```
to get UUIDs for reviewer assignment

在执行操作前，请始终将人类可读名称解析为对应的ID：

工作区: 通过
```
BITBUCKET_LIST_WORKSPACES
```
获取工作区别名
仓库: 通过
```
BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE
```
并结合
```
q
```
筛选条件找到仓库别名
分支: 在创建PR前，通过
```
BITBUCKET_LIST_BRANCHES
```
验证分支是否存在
成员: 通过
```
BITBUCKET_LIST_WORKSPACE_MEMBERS
```
获取用于指定评审人的UUID

Pagination

分页

Bitbucket uses page-based pagination (not cursor-based):

Use
```
page
```
(starts at 1) and
```
pagelen
```
(items per page) parameters
Default page size is typically 10; set
```
pagelen
```
explicitly (max 50 for PRs, 100 for others)
Check response for
```
next
```
URL or total count to determine if more pages exist
Always iterate through all pages for complete results

Bitbucket使用基于页码的分页（而非游标分页）:

使用
```
page
```
（从1开始）和
```
pagelen
```
（每页结果数）参数
默认每页大小通常为10条；请显式设置
```
pagelen
```
参数（PR的最大值为50，其他操作最大值为100）
检查响应中的
```
next
```
链接或总结果数，以判断是否存在更多页面
如需获取完整结果，请始终遍历所有页面

BBQL Filtering

BBQL筛选

Bitbucket Query Language is available on list endpoints:

String values MUST use double quotes:
```
name~"pattern"
```
Operators:
```
=
```
(exact),
```
~
```
(contains),
```
!=
```
(not equal),
```
>
```
,
```
>=
```
,
```
<
```
,
```
<=
```
Combine with
```
AND
```
/
```
OR
```
:
```
name~"api" AND is_private=true
```

列表类接口支持Bitbucket查询语言（BBQL）:

字符串值必须使用双引号：
```
name~"pattern"
```
支持的运算符：
```
=
```
（精确匹配）、
```
~
```
（包含匹配）、
```
!=
```
（不相等）、
```
>
```
、
```
>=
```
、
```
<
```
、
```
<=
```
可通过
```
AND
```
/
```
OR
```
组合条件：
```
name~"api" AND is_private=true
```

Known Pitfalls

已知注意事项

ID Formats

ID格式

Workspace: slug string (e.g.,
```
my-workspace
```
) or UUID in braces (
```
{uuid}
```
)
Reviewer UUIDs must include curly braces:
```
{123e4567-e89b-12d3-a456-426614174000}
```
Issue IDs are strings; PR IDs are integers in some tools, strings in others
Commit hashes must be full SHA1 (40 characters)

工作区：字符串别名（例如
```
my-workspace
```
）或带大括号的UUID（
```
{uuid}
```
）
评审人UUID必须包含大括号：
```
{123e4567-e89b-12d3-a456-426614174000}
```
问题ID为字符串；PR ID在部分工具中为整数，在其他工具中为字符串
提交哈希必须是完整的SHA1值（40个字符）

Parameter Quirks

参数特殊说明

```
assignee
```
vs
```
assignee_account_id
```
: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUID
```
state
```
values for issues include spaces:
```
"on hold"
```
, not
```
"on_hold"
```
```
destination_branch
```
omission defaults to repo main branch, not
```
main
```
literally
BBQL
```
repository
```
is not a valid field -- use
```
name
```

assignee

与

assignee_account_id

的区别：

CREATE_ISSUE

使用用户名，

UPDATE_ISSUE

使用UUID

问题的
```
state
```
参数部分值包含空格：
```
"on hold"
```
，而非
```
"on_hold"
```
若省略
```
destination_branch
```
，默认使用仓库的主分支，但该分支名称不一定是
```
main
```
BBQL中
```
repository
```
不是有效字段，请使用
```
name
```
替代

Rate Limits

速率限制

Bitbucket Cloud API has rate limits; large batch operations should include delays
Paginated requests count against rate limits; minimize unnecessary page fetches

Bitbucket Cloud API存在速率限制；大型批量操作应添加延迟
分页请求会占用速率限制配额；请尽量减少不必要的页面请求

Destructive Operations

破坏性操作

```
BITBUCKET_DELETE_REPOSITORY
```
is irreversible and does not remove forks
```
BITBUCKET_DELETE_ISSUE
```
is permanent with no recovery option
Always confirm with the user before executing delete operations

```
BITBUCKET_DELETE_REPOSITORY
```
操作不可恢复，且不会删除派生仓库
```
BITBUCKET_DELETE_ISSUE
```
操作永久生效，无法恢复
在执行删除操作前，请始终与用户确认

Quick Reference

快速参考

Task	Tool Slug	Key Params
List workspaces	`BITBUCKET_LIST_WORKSPACES`	`q` , `sort`
List repos	`BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE`	`workspace` , `q` , `role`
Create repo	`BITBUCKET_CREATE_REPOSITORY`	`workspace` , `repo_slug` , `is_private`
Delete repo	`BITBUCKET_DELETE_REPOSITORY`	`workspace` , `repo_slug`
List branches	`BITBUCKET_LIST_BRANCHES`	`workspace` , `repo_slug` , `q`
Create branch	`BITBUCKET_CREATE_BRANCH`	`workspace` , `repo_slug` , `name` , `target_hash`
List PRs	`BITBUCKET_LIST_PULL_REQUESTS`	`workspace` , `repo_slug` , `state`
Create PR	`BITBUCKET_CREATE_PULL_REQUEST`	`workspace` , `repo_slug` , `title` , `source_branch`
Get PR details	`BITBUCKET_GET_PULL_REQUEST`	`workspace` , `repo_slug` , `pull_request_id`
Get PR diff	`BITBUCKET_GET_PULL_REQUEST_DIFF`	`workspace` , `repo_slug` , `pull_request_id` , `max_chars`
Get PR diffstat	`BITBUCKET_GET_PULL_REQUEST_DIFFSTAT`	`workspace` , `repo_slug` , `pull_request_id`
Comment on PR	`BITBUCKET_CREATE_PULL_REQUEST_COMMENT`	`workspace` , `repo_slug` , `pull_request_id` , `content_raw`
List issues	`BITBUCKET_LIST_ISSUES`	`workspace` , `repo_slug` , `state` , `priority`
Create issue	`BITBUCKET_CREATE_ISSUE`	`workspace` , `repo_slug` , `title` , `content`
Update issue	`BITBUCKET_UPDATE_ISSUE`	`workspace` , `repo_slug` , `issue_id`
Comment on issue	`BITBUCKET_CREATE_ISSUE_COMMENT`	`workspace` , `repo_slug` , `issue_id` , `content`
Delete issue	`BITBUCKET_DELETE_ISSUE`	`workspace` , `repo_slug` , `issue_id`
List members	`BITBUCKET_LIST_WORKSPACE_MEMBERS`	`workspace`

任务	工具标识	关键参数
列出工作区	`BITBUCKET_LIST_WORKSPACES`	`q` , `sort`
列出仓库	`BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE`	`workspace` , `q` , `role`
创建仓库	`BITBUCKET_CREATE_REPOSITORY`	`workspace` , `repo_slug` , `is_private`
删除仓库	`BITBUCKET_DELETE_REPOSITORY`	`workspace` , `repo_slug`
列出分支	`BITBUCKET_LIST_BRANCHES`	`workspace` , `repo_slug` , `q`
创建分支	`BITBUCKET_CREATE_BRANCH`	`workspace` , `repo_slug` , `name` , `target_hash`
列出PR	`BITBUCKET_LIST_PULL_REQUESTS`	`workspace` , `repo_slug` , `state`
创建PR	`BITBUCKET_CREATE_PULL_REQUEST`	`workspace` , `repo_slug` , `title` , `source_branch`
获取PR详情	`BITBUCKET_GET_PULL_REQUEST`	`workspace` , `repo_slug` , `pull_request_id`
获取PR差异对比	`BITBUCKET_GET_PULL_REQUEST_DIFF`	`workspace` , `repo_slug` , `pull_request_id` , `max_chars`
获取PR差异统计	`BITBUCKET_GET_PULL_REQUEST_DIFFSTAT`	`workspace` , `repo_slug` , `pull_request_id`
评论PR	`BITBUCKET_CREATE_PULL_REQUEST_COMMENT`	`workspace` , `repo_slug` , `pull_request_id` , `content_raw`
列出问题	`BITBUCKET_LIST_ISSUES`	`workspace` , `repo_slug` , `state` , `priority`
创建问题	`BITBUCKET_CREATE_ISSUE`	`workspace` , `repo_slug` , `title` , `content`
更新问题	`BITBUCKET_UPDATE_ISSUE`	`workspace` , `repo_slug` , `issue_id`
评论问题	`BITBUCKET_CREATE_ISSUE_COMMENT`	`workspace` , `repo_slug` , `issue_id` , `content`
删除问题	`BITBUCKET_DELETE_ISSUE`	`workspace` , `repo_slug` , `issue_id`
列出工作区成员	`BITBUCKET_LIST_WORKSPACE_MEMBERS`	`workspace`