Skip to main content
Glama
Bitbucket MCP Server
by pdogra1299

create_pull_request

Create a Bitbucket pull request to propose merging source branch changes into a destination branch, with optional reviewers, description, and attachments.

Instructions

Create a pull request.

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": {
      "workspace": "<workspace>",
      "repository": "<repository>",
      "title": "<title>",
      "source_branch": "<source_branch>",
      "destination_branch": "<destination_branch>"
    },
    "name": "create_pull_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
reviewersNoReviewer usernames
workspaceYesProject key (e.g., PROJ)
repositoryYesRepository slug
attachmentsNoLocal files to upload & embed (Server/DC only). Item: path string or {file_path, alt_text?, render?: image|link|auto}
descriptionNo
source_branchYes
destination_branchYes
close_source_branchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.0.1
    • addedInput schema / properties / attachments
      Added value: +{
      +  "description": "Local files to upload & embed (Server/DC only). Item: path string or {file_path, alt_text?, render?: image|link|auto}",
      +  "items": {
      +    "oneOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "properties": {
      +          "alt_text": {
      +            "type": "string"
      +          },
      +          "file_path": {
      +            "type": "string"
      +          },
      +          "render": {
      +            "enum": [
      +              "image",
      +              "link",
      +              "auto"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "file_path"
      +        ],
      +        "type": "object"
      +      }
      +    ]
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / close_source_branch / description
      Removed value: -"Whether to close source branch after merge (optional, default: false)"
    • removedInput schema / properties / description / description
      Removed value: -"Description of the pull request (optional)"
    • removedInput schema / properties / destination_branch / description
      Removed value: -"Destination branch name (e.g., \"main\", \"master\")"
    • changedInput schema / properties / repository / description
      Previous value: -"Repository slug (e.g., \"my-repo\")"New value: +"Repository slug"
    • changedInput schema / properties / reviewers / description
      Previous value: -"Array of reviewer usernames/emails (optional)"New value: +"Reviewer usernames"
    • removedInput schema / properties / source_branch / description
      Removed value: -"Source branch name"
    • removedInput schema / properties / title / description
      Removed value: -"Title of the pull request"
    • changedInput schema / properties / workspace / description
      Previous value: -"Bitbucket workspace/project key (e.g., \"PROJ\")"New value: +"Project key (e.g., PROJ)"
  2. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of required permissions, whether the source branch must exist, side effects, or error behavior for a five-required-parameter mutation.

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

Conciseness2/5

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

It is a single short sentence, so there is no bloat, but this is under-specification rather than conciseness. The one sentence fails to earn its place by conveying anything not already in the name.

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

Completeness1/5

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

For a nine-parameter mutation tool with five required fields, no output schema, and incomplete schema documentation, the description is wholly inadequate. It provides no information about branch handling, reviewers, attachments, or the result of the call.

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

Parameters1/5

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

Schema description coverage is only 44%, and the description mentions no parameters at all. Critical fields like title, description, source_branch, destination_branch, and close_source_branch have no schema descriptions and receive no clarification from the description, leaving the agent to guess semantics.

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

Purpose2/5

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

The sentence restates the tool name almost verbatim ('Create a pull request' for create_pull_request), giving no scope, target system, or distinguishing detail. It does convey a write action on a pull request resource, but nothing separates it from siblings like update_pull_request or merge_pull_request.

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 versus update_pull_request, merge_pull_request, or decline_pull_request, nor any prerequisite conditions such as branch existence or permissions. The agent must infer everything from the tool name.

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