Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get pull request comments and action items

bb_get_pr_comments_and_actions

Retrieve pull request review comment threads with severity, open/resolved state, and action tasks to triage feedback; resolved threads stay hidden unless requested.

Instructions

Read the review discussion of a pull request as threads: comment severity (NORMAL/BLOCKER), thread state (OPEN/RESOLVED) and action tasks. Resolved threads are hidden unless includeResolved=true. On Cloud severity is recognized from the '[BLOCKER]' text prefix written by bb_post_pull_request_comment.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number (Cloud only).
limitNoComments per page (max 1000).
startNoZero-based page offset (Server/DC).
severityNoOnly return threads with this severity.ALL
projectKeyYesProject key (on Cloud: workspace slug).
maxTextCharsNoMaximum characters per comment text.
pullRequestIdYesPull request id.
includeRepliesNoInclude reply comments inside each thread.
repositorySlugYesRepository slug.
includeResolvedNoInclude threads that are resolved (thread itself or any reply). Default: hidden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full disclosure burden and does address the two non-obvious behaviors: resolved threads (or threads with a resolved reply) are silently filtered out by default, and on Cloud severity is derived from a '[BLOCKER]' text prefix rather than a structured field. It omits any statement about idempotency, permissions, or pagination behavior, which keeps it short of 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.

Conciseness5/5

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

Three tight sentences: output shape first, then the hidden-by-default filter rule, then the Cloud-specific severity caveat. Nothing is repeated from the name and no sentence is filler.

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?

With 10 parameters, no annotations, and no output schema, the description does the important work of sketching the return structure as threads and flagging the default filtering rule. Remaining gaps are minor — it does not explain what an 'action task' contains or that paging differs between page (Cloud) and start (Server), the latter being left to the schema.

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 the baseline is 3, but the description adds real meaning beyond the schema by explaining how severity is actually determined on Cloud (the '[BLOCKER]' prefix written by bb_post_pull_request_comment) — the enum alone would not tell an agent that. It also reinforces the includeResolved default semantics at the behavior level rather than as a field note.

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 states a specific verb and resource ('Read the review discussion of a pull request') and immediately names the shape of what comes back: threads with comment severity, thread state, and action tasks. That is enough to separate it from metadata-oriented siblings such as bb_get_pull_request or bb_get_pull_request_changes without opening a schema.

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 rather than stated: it tells the agent that resolved threads are hidden by default unless includeResolved=true, which is genuinely useful selection context. However, it never says when to prefer this tool over adjacent ones (e.g. diff/changes tools) and gives no exclusions, so guidance stays at the inferred level.

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