Atlassian Bamboo MCP Server

by norus

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

bamboo_list_projects

Retrieve a list of all Bamboo projects with optional pagination and expandable fields for detailed project information.

Instructions

List all Bamboo projects

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bamboo_list_projects"
  }
}

Input Schema

Name	Required	Description
`expand`	No	Fields to expand in the response (e.g., "projects.project.plans")
`max_results`	No	Maximum number of results to return (default: 25)
`start_index`	No	Starting index for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 29, 2026

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 should disclose behavioral traits such as read-only nature, pagination behavior, or potential limits, but it does not.

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 concise sentence that gets straight to the point with no extraneous information.

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 lack of output schema and no description of return values or behavior, the description is incomplete for a list tool with optional pagination parameters.

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 parameters are already explained in the schema. The description adds no additional meaning beyond the schema.

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 'List all Bamboo projects' clearly states the action (list) and the resource (projects), distinguishing it from sibling tools that list plans, build results, etc.

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 bamboo_list_plans or bamboo_list_build_results, or when not to use it.

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