Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Update pull request comment

bb_update_pull_request_comment

Edit pull request comment text or severity, resolve or reopen its thread, or change a comment task's state using project, repository, pull request, and comment identifiers.

Instructions

Update a comment's text or severity, resolve/unresolve its thread (state=RESOLVED|OPEN), or reopen/close one of its tasks (taskId+taskState). Server/DC uses optimistic locking (re-fetch + one retry on 409); Cloud applies single PUTs and has no severity field (the '[BLOCKER]' text tag is the convention).

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>",
      "commentId": "<commentId>"
    },
    "name": "bb_update_pull_request_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoNew comment text.
stateNoThread state (RESOLVED resolves the thread).
taskIdNoTask id to update (requires taskState).
severityNoNew severity (Server/DC only; echoed with a note on Cloud).
commentIdYesComment id to update.
taskStateNoNew task state (requires taskId).
projectKeyYesProject key (on Cloud: workspace slug).
pullRequestIdYesPull request id.
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses Server/DC optimistic locking with re-fetch plus a single retry on 409, notes Cloud uses single PUTs, and explains that severity is unsupported on Cloud where a '[BLOCKER]' text tag is the convention. It omits permission requirements and what a partial update does to fields not supplied, which keeps it below a 5.

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 dense sentence front-loads the three action modes before the platform caveats, so an agent gets the essential routing information first. It is close to run-on and the parenthetical enum hints partially duplicate the schema, but no sentence is wasted.

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 9-parameter mutation tool with no annotations and no output schema, the description covers the hard parts: multi-mode routing and the Server/DC vs Cloud divergence including locking and severity handling. It leaves out permission prerequisites and any indication of what the response contains, which is a modest gap given the absence of an output schema.

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 every parameter, including the taskId/taskState pairing and the OPEN/RESOLVED enums; the description largely restates this. The one genuine addition beyond the schema is the Cloud '[BLOCKER]' text-tag convention for severity, which justifies the baseline rather than exceeding it.

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?

States a specific verb (update) and resource (pull request comment), then enumerates the three distinct modes of operation: text/severity edits, thread state changes, and task state changes. An agent can tell this apart from the create-oriented sibling bb_post_pull_request_comment and the read-oriented bb_get_pr_comments_and_actions without opening any schema.

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

Usage Guidelines4/5

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

The description acts as a routing guide by tying each action to its parameter combination (state=RESOLVED|OPEN for thread resolution, taskId+taskState for tasks). It does not state prerequisites such as required permissions or specify when a caller should instead delete/re-post a comment, so it stops short of explicit when-not guidance.

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