Skip to main content
Glama
Sign In
Bitbucket MCP Server

Bitbucket MCP Server

by ATERCATES
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getPipelineRun

Fetch details of a specific Bitbucket pipeline run by providing workspace, repo slug, and pipeline UUID.

Instructions

Get details for a specific pipeline run

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": {
      "workspace": "<workspace>",
      "repo_slug": "<repo_slug>",
      "pipeline_uuid": "<pipeline_uuid>"
    },
    "name": "getPipelineRun"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoWhen true (and no page is provided), automatically follows Bitbucket next links to return all items up to 1000.
pageNoBitbucket page number to fetch (1-based).
pagelenNoNumber of items per page (Bitbucket pagelen). Defaults to 10 and caps at 100.
repo_slugYesRepository slug
workspaceYesBitbucket workspace name
pipeline_uuidYesPipeline UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'get details', which is insufficient—no mention of authentication, rate limits, pagination behavior, or what the response includes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence of seven words, which is concise but lacks structure. It does not front-load key information or use bullet points, but it is not overly verbose.

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?

Given the tool has 6 parameters (3 required) and no output schema, the description omits details about return values and pagination behavior. Among many similar sibling tools, more context is needed for correct selection.

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 input schema fully documents each parameter. The description adds no extra meaning beyond what the schema already provides, warranting a baseline score of 3.

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 clearly states the verb 'Get' and the resource 'details for a specific pipeline run'. It effectively distinguishes from sibling tools like getPipelineStep and getPipelineSteps by specifying 'pipeline run'.

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?

No guidance on when to use this tool versus alternatives. The description does not mention any context or exclusions, leaving the agent to infer usage from the name alone.

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

Deploy Server

Other Tools