bitbucket-mcp-server

trigger-pipeline

Starts a new Bitbucket pipeline run for a specified repository, branch, tag, or commit, with optional environment variables and custom pipeline selectors.

Instructions

Trigger a new pipeline for a repository

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": "trigger-pipeline"
  }
}

Input Schema

Name	Required	Description
`ref_name`	No	Name of the branch or tag
`ref_type`	No	Type of reference (branch or tag)
`repo_slug`	Yes	Repository slug/name
`variables`	No	Environment variables for the pipeline (key-value pairs)
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
`commit_hash`	No	Full hash of the commit to run the pipeline on
`selector_type`	No	Type of selector (e.g., 'custom', 'default')
`selector_pattern`	No	Pattern for the selector (e.g., custom pipeline name)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It states that a pipeline is triggered but omits side effects, authentication requirements, whether the call is synchronous or asynchronous, idempotency, and what is returned.

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 single sentence is front-loaded and contains no wasted words. However, for a complex mutation with eight parameters, this size is under-specified rather than appropriately concise.

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?

This is a mutation tool with eight parameters, a nested variables object, no annotations, and no output schema. The one-line description conveys only the basic purpose and leaves out behavior, authorization context, and result semantics needed for safe invocation.

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%, and all eight parameters including the nested variables object and the ref_type enum are documented in the schema. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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?

States a specific action and resource: 'Trigger a new pipeline for a repository'. This distinguishes it from read-oriented siblings such as pipelines and pipeline-steps, but it does not explicitly differentiate itself from those alternatives.

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?

Provides no when-to-use guidance, no exclusions, and no mention of alternatives like listing pipelines or inspecting pipeline steps. Any usage context is only implied by the verb 'Trigger'.

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

Deploy Server