Skip to main content
Glama

bitbucket_pull_requests

List, create, update, merge, approve, decline pull requests, manage comments, and retrieve details and diffs on Bitbucket repositories.

Instructions

Manage Bitbucket pull requests. Actions:

  • list: List pull requests in a repository

  • get: Get pull request details

  • create: Create a new pull request

  • update: Update a pull request

  • merge: Merge a pull request

  • approve: Approve a pull request

  • unapprove: Remove approval from a pull request

  • decline: Decline a pull request

  • list_comments: List comments on a pull request

  • add_comment: Add a comment to a pull request

  • get_diff: Get the diff of a pull request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
workspaceNoWorkspace slug (uses BITBUCKET_WORKSPACE env if omitted)
repo_slugYesRepository slug
pr_idNoPull request ID (required for most actions except list/create)
stateNoFilter by state
qNoQuery string to filter PRs
sortNoSort field (e.g., "-created_on")
titleNoPull request title
descriptionNoPull request description
source_branchNoSource branch name
destination_branchNoDestination branch (default: main branch)
close_source_branchNoClose source branch after merge
reviewersNoList of reviewer UUIDs
merge_strategyNoMerge strategy
messageNoMerge commit message
contentNoComment content (markdown supported)
inline_pathNoFile path for inline comment (requires inline_line)
inline_lineNoLine number for inline comment (requires inline_path)
parent_idNoParent comment ID for replies
pageNoPage number for pagination
pagelenNoResults per page (default: 25, max 100)
formatNoOutput format: json (full), toon (compact tokens), compact (essential fields only)
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as side effects (e.g., merge finalizes the PR), required permissions, rate limits, or error handling. The action names imply behavior but lack explicit context.

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

Conciseness5/5

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

The description is extremely concise: two sentences—the first stating the purpose, the second a bullet list of actions. No redundant information, effectively front-loaded.

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?

Despite high complexity (22 parameters, 11 actions), the description lacks behavioral details, usage context, and outcome explanations. The output schema is absent, and the description does not compensate, leaving significant gaps.

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%, so the schema already documents all parameters. The description adds no extra meaning beyond listing actions, achieving the baseline score of 3.

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

Purpose5/5

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

The description clearly states 'Manage Bitbucket pull requests' and enumerates 11 specific actions (list, get, create, update, merge, approve, etc.), distinguishing the tool from sibling tools that cover branches, commits, issues, etc.

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?

The description lists actions but provides no guidance on when to use this tool versus alternatives (e.g., bitbucket_branches for branch management) or when to use specific actions like create vs update.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icy-r/bitbucket-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server