Skip to main content
Glama
Sign In
Bitbucket MCP Server

Bitbucket MCP Server

by ATERCATES
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stopPipeline

Stop a running Bitbucket pipeline by providing workspace, repository slug, and pipeline UUID.

Instructions

Stop a running pipeline

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": "stopPipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_slugYesRepository slug
workspaceYesBitbucket workspace name
pipeline_uuidYesPipeline UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Stop a running pipeline' without explaining side effects, permissions required, or whether the action is reversible.

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?

The description is a single clear sentence, front-loaded with the action. However, it could be slightly more informative without sacrificing brevity.

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 straightforward stop action with no output schema, the description is minimally adequate but could mention expected outcomes or error conditions.

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%, providing descriptions for all three parameters. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 'Stop' and the resource 'pipeline', indicating exactly what action is performed. It distinguishes from sibling tools like runPipeline.

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?

The description lacks guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., pipeline must be running) or when not to use it (e.g., pipeline already completed).

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