bitbucket-mcp-server

resolve-pr-comment

Resolve or unresolve a Bitbucket pull request comment thread by specifying the repository, pull request, comment ID, and desired action.

Instructions

Resolve or unresolve a pull request comment thread

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>",
      "pull_request_id": "<pull_request_id>",
      "comment_id": "<comment_id>",
      "action": "<action>"
    },
    "name": "resolve-pr-comment"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Whether to resolve or unresolve the comment thread
`repo_slug`	Yes	Repository slug/name
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
`comment_id`	Yes	Top-level comment ID for the thread to resolve or unresolve
`pull_request_id`	Yes	Pull request ID

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?

With no annotations, the description carries the full burden of behavioral disclosure for a mutation tool, and it discloses almost nothing: no permission requirements, no idempotency behavior for already-resolved or already-unresolved threads, no side effects such as notifications, and no statement of what is returned. The only implicit behavior is reversibility, conveyed by the 'unresolve' option itself.

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 clause with zero wasted words. It is efficient, though the absence of any secondary sentence leaves it without structure for usage or behavioral notes.

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 a mutation tool with no annotations and no output schema, one line is not enough: the agent cannot learn required permissions, error or no-op behavior on already-resolved threads, or what the call returns. The schema covers inputs fully, but the behavioral surface is left undocumented.

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 every parameter including the action enum and the workspace env-var fallback is already documented in the schema. The description adds no parameter-level meaning beyond that, which is the baseline case for full coverage.

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 pair (resolve/unresolve) and a specific resource (pull request comment thread), which is enough for an agent to distinguish it from siblings like pr-comments or create-pr-comment. It stops short of naming what it is not, so it is clear but not maximally differentiated.

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 when-to-use guidance, no prerequisites (e.g., required Bitbucket permissions or scopes), and no mention of alternatives or exclusions. The only usage signal is the action enum in the schema, which the description does not elaborate on.

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

Deploy Server