Bitbucket Cloud MCP Server

trigger_pipeline

Start a new pipeline run on a Bitbucket Cloud repository branch, tag, or bookmark to automate build, test, and deployment workflows.

Instructions

Trigger a new pipeline run on a branch, tag, or bookmark.

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>",
      "ref_type": "<ref_type>",
      "ref_name": "<ref_name>"
    },
    "name": "trigger_pipeline"
  }
}

Input Schema

Name	Required	Description
`workspace`	Yes	The workspace slug
`repo_slug`	Yes	The repository slug
`ref_type`	Yes	Reference type
`ref_name`	Yes	Reference name (branch/tag name)
`variables`	No	Pipeline variables

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 29, 2025

TDQS

C2.9/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 but only states the action without behavioral details. It doesn't disclose whether this is a mutating operation (implied by 'trigger'), what permissions are required, whether it's idempotent, rate limits, or what happens if a pipeline is already running. For a tool that likely modifies system state, this is a significant transparency gap.

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?

The description is a single, efficient sentence that front-loads the core action and scope. Every word contributes essential information with zero redundancy. It's appropriately sized for a tool with clear parameters documented elsewhere.

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 mutating tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after triggering (e.g., returns a pipeline ID, runs asynchronously), error conditions, or system impact. Given the complexity of pipeline execution and the lack of structured behavioral information, this leaves significant gaps for an agent.

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 parameters are well-documented in the schema itself. The description adds minimal value beyond the schema by mentioning 'branch, tag, or bookmark' which corresponds to the 'ref_type' enum, but doesn't explain parameter relationships or provide additional context about how these parameters interact during pipeline triggering.

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 clearly states the action ('trigger') and target ('new pipeline run') with specific scope ('on a branch, tag, or bookmark'), making the purpose immediately understandable. It distinguishes from siblings like 'stop_pipeline' or 'get_pipeline' by focusing on initiation rather than termination or retrieval. However, it doesn't explicitly differentiate from all pipeline-related tools in context.

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 is provided on when to use this tool versus alternatives like 'stop_pipeline' or 'list_pipelines'. The description mentions triggering on specific reference types but doesn't explain prerequisites, dependencies, or typical use cases. Without annotations, this leaves the agent with insufficient context for optimal tool selection.

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