Atlassian Bamboo MCP Server

by norus

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

bamboo_create_deployment_project

Create a new deployment project linked to a build plan to automate deployments.

Instructions

Create a new Bamboo deployment project linked to a build plan

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": {
      "name": "<name>",
      "plan_key": "<plan_key>"
    },
    "name": "bamboo_create_deployment_project"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the deployment project
`plan_key`	Yes	Build plan key to link (e.g., "PROJ-PLAN")
`description`	No	Description of the deployment project

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does ('Create a new ...') but does not disclose side effects, authorization needs, idempotency, or error behavior (e.g., duplicate name handling). This is insufficient for a mutation tool.

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, front-loaded sentence that uses every word purposefully. There is no extraneous information, making it highly concise. It clearly states the core action and key constraint without waste.

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 complexity of a creation tool with no output schema and no annotations, the description is too minimal. It does not explain what the tool returns (e.g., project ID or status), nor does it cover error conditions or asynchronous behavior. The agent lacks essential information to handle the tool's output or potential failures.

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?

The input schema provides 100% coverage with descriptions for all three parameters. The tool description adds no new information beyond what the schema already conveys; it merely repeats the linking aspect of plan_key. Baseline score of 3 is appropriate since schema does the heavy lifting.

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 specifies the verb 'Create' and the resource 'Bamboo deployment project', and includes the key constraint 'linked to a build plan'. This distinguishes it from sibling tools, which are all retrieval, listing, or trigger operations, and no other tool creates a deployment project.

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 description does not provide any guidance on when to use this tool or alternatives. While it is the only creation tool among siblings, there is no mention of prerequisites (e.g., the plan key must exist) or scenarios where this tool should not be used. The description is functional but lacks explicit usage context.

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