Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Submit pull request review

bb_submit_pull_request_review

Submit an APPROVED, NEEDS_WORK, or UNAPPROVED review verdict on a Bitbucket pull request, with automatic reviewer resolution and best-effort draft publishing where supported.

Instructions

Submit a review verdict (APPROVED | NEEDS_WORK | UNAPPROVED). Server/DC: best-effort publishing of pending drafts first, reviewer identity resolved automatically (userSlug → session user → activity consensus → single participant → userFilter). Cloud: reviews always act as the authenticated user (a mismatching userSlug is rejected), NEEDS_WORK maps to 'request changes', no pending drafts exist.

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": {
      "projectKey": "<projectKey>",
      "repositorySlug": "<repositorySlug>",
      "pullRequestId": "<pullRequestId>",
      "verdict": "<verdict>"
    },
    "name": "bb_submit_pull_request_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
verdictYesReview verdict to submit.
userSlugNoReviewer slug; resolved automatically when omitted (must match the configured account on Cloud).
projectKeyYesProject key (on Cloud: workspace slug).
userFilterNoFallback: disambiguate your user by name/email filter (Server/DC only).
pullRequestIdYesPull request id.
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the whole burden and does substantial work: it discloses the side effect of best-effort publishing of pending drafts on Server/DC, the reviewer-identity resolution chain, the Cloud rejection of a mismatching userSlug, and the NEEDS_WORK → 'request changes' mapping. It omits whether a submitted verdict can be re-submitted/overwritten and what the response contains, so not a full 5.

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?

Front-loaded with the action and the verdict values, then cleanly partitioned into Server/DC versus Cloud behavior. Dense but every clause carries information an agent needs; there is no filler or restatement of the name.

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

Completeness4/5

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

For a 6-parameter mutation with no output schema and no annotations, the definition covers the enum semantics, identity resolution, and the two platform behavior paths. What an agent still cannot know is the return value and whether a repeat submit replaces an existing review verdict.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond it: the ordered resolution chain for userSlug (session user → activity consensus → single participant → userFilter) and the explicit Server/DC-only scoping of userFilter. That is genuine context the schema's per-field text does not provide.

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?

States a specific verb and resource ('Submit a review verdict') and enumerates the three verdicts inline, which makes it unmistakable against siblings like bb_post_pull_request_comment or bb_merge_pull_request. It stops short of naming a sibling it is not, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is implied by the verdict enum (approve / request changes / unapprove) and the platform notes, so an agent can infer when to call it. There is no explicit when-not guidance, no statement of alternatives (e.g. use the comment tool to leave non-verdict feedback), and no prerequisite conditions spelled out.

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