bitbucket-mcp-server

pipelines

List repository CI/CD runs or fetch details for a single run by UUID in Bitbucket.

Instructions

List pipelines for a repository, or get details for a single pipeline when pipeline_uuid is provided.

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

Input Schema

Name	Required	Description
`page`	No	(list only) Page number or opaque next page URL
`pagelen`	No	(list only) Items per page (10-100, default 10)
`repo_slug`	Yes	Repository slug/name
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
`pipeline_uuid`	No	Pipeline UUID. If provided, returns a single pipeline; otherwise lists all pipelines.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the important mode-switch behavior (single pipeline versus list) and implies a read-only operation, but says nothing about permissions, pagination behavior, or result shape. That is thin for an unannotated tool, though the core conditional behavior is at least stated.

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?

A single sentence with zero filler, front-loading the primary list operation before the conditional detail mode. Nothing in it is redundant or padding.

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 five parameters, one required, full schema coverage, and no output schema, the description covers enough for correct invocation: an agent knows the required repo_slug and what pipeline_uuid does. The remaining gap is how paged results behave, which the schema partially covers but the description never touches.

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 description coverage is 100%, so the baseline is 3, and the description's only parameter claim, that pipeline_uuid selects single-pipeline detail, is already documented in the schema property text. It adds no syntax, format, or default information beyond the schema, but it does correctly frame the parameter's role in the tool's two modes.

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?

The description names a specific verb and resource (list/get pipelines) and covers both operating modes, list-for-repo and single-by-uuid, in one clause. It does not explicitly distinguish itself from sibling tools such as pipeline-steps or trigger-pipeline, so an agent must still guess how this differs from those, which keeps it below 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?

The conditional 'when pipeline_uuid is provided' gives implied guidance for choosing between the two modes, which is useful. There is no guidance on when to reach for this tool versus pipeline-steps or trigger-pipeline, and no stated prerequisites such as workspace or auth context.

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

Deploy Server