bitbucket-mcp-server

create-pull-request

Open a new Bitbucket pull request by specifying the repository, title, and source branch; optionally set reviewers, description, destination branch, and close-source behavior.

Instructions

Create a new pull request in a repository

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo_slug": "<repo_slug>",
      "title": "<title>",
      "source_branch": "<source_branch>"
    },
    "name": "create-pull-request"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Title of the pull request
`repo_slug`	Yes	Repository slug/name
`reviewers`	No	List of reviewer account UUIDs (e.g. '{account-uuid}')
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
`description`	No	Description of the pull request (supports Markdown)
`source_branch`	Yes	Source branch name (the branch with your changes)
`destination_branch`	No	Destination branch name (defaults to the repository's main branch)
`close_source_branch`	No	Whether to close the source branch after the PR is merged

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It confirms this is a mutation, but says nothing about required permissions, what happens on duplicate PRs, whether the source branch must already exist remotely, or whether reviewers are notified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero padding or redundant phrasing. It is efficient, though its brevity reflects under-specification rather than disciplined compression.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter mutation tool with no annotations and no output schema, one sentence is far too thin. Nothing is said about the create semantics, error conditions, or what the caller receives back, leaving the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each of the eight parameters is documented in the schema, including defaults and env-var fallback, so the baseline is 3. The description adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Create a new pull request') and scopes it to a repository, so an agent immediately knows the operation. It stops short of distinguishing this tool from siblings like 'update-pr-description' or 'create-pr-comment', which also touch pull request content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, and no mention of preconditions such as needing an existing branch, pushing commits first, or being authenticated. The agent is left to infer all of that from the tool name and schema.

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

Deploy Server