Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get pull request build statuses

bb_get_pull_request_builds

Fetches CI build statuses for a pull request's source-branch head commit, helping you verify checks passed before merging or reviewing.

Instructions

Fetch the CI build statuses attached to the pull request's source-branch head commit (build-state integration).

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_pull_request_builds"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number (Cloud only; from nextPageStart of the previous call). Ignored on Server/DC.
limitNoPage size (1-1000).
startNoZero-based page offset (Server/DC).
projectKeyYesProject key (on Cloud: workspace slug).
pullRequestIdYesPull request id, e.g. 101.
repositorySlugYesRepository slug, e.g. 'service-api'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the whole behavioral burden and it does disclose one genuinely useful trait: builds are keyed to the source-branch head commit, not the merge commit or earlier commits. It does not cover auth/permission needs, empty-result behavior, or result freshness, which matters for a status tool.

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 sentence with the scope constraint front-loaded and zero filler. The parenthetical '(build-state integration)' is mildly cryptic but does not obstruct comprehension.

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

Completeness3/5

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

For a six-parameter, three-required tool with no output schema, the definition never indicates what a build status object contains (state, key, name, url) or how results are ordered/limited. Adequate to call correctly, thin for interpreting what comes back.

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 coverage is 100%, so all six parameters (projectKey, repositorySlug, pullRequestId, page, start, limit) are already documented, including the Cloud-vs-Server/DC paging split. The description adds no parameter-level meaning, so baseline 3 applies.

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 (Fetch) and resource (CI build statuses) and pins the exact scope: the pull request's source-branch head commit. No sibling returns build data, so an agent can route here unambiguously without opening another 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?

The head-commit scoping implies when the tool is relevant (checking whether the PR's tip builds green), but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage must be inferred from the resource description alone.

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