Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

List Bitbucket projects

bb_get_projects

Lists Bitbucket Server/Data Center projects with optional name filtering and pagination metadata, so you can browse compact project cards.

Instructions

List projects on the Bitbucket Server / Data Center instance. Supports an optional server-side name filter. Returns compact project cards with paging metadata (isLastPage / nextPageStart).

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

Input Schema

NameRequiredDescriptionDefault
nameNoFilter projects by name (server-side filter on Server/DC, client-side on Cloud).
pageNoOne-based page number (Cloud only; from nextPageStart of the previous call). Ignored on Server/DC.
limitNoPage size (1-1000).
startNoZero-based page offset (Server/DC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful traits beyond structured data: that filtering is server-side, and that results are compact project cards with paging metadata (isLastPage / nextPageStart). However, it omits permissions or authentication requirements and does not reconcile the Server/DC paging model with the Cloud paging model, even though it says "server-side" while the schema says the filter is client-side on Cloud.

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?

Three tight sentences, front-loaded with the operation and then the filter and return shape. No filler, no repetition of the title, and every sentence carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-optional-parameter list tool with full schema coverage and no output schema, this covers the essentials: what is listed, the filter behavior, and the shape of the response including paging fields. The gap is deployment-specific behavior, specifically Cloud versus Server/DC paging divergence, which the schema handles but the description does not surface.

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 baseline is 3. The description adds little beyond the schema, and it slightly conflicts with it: the description calls the name filter unconditionally server-side, while the schema correctly notes it is client-side on Cloud.

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?

Specific verb plus resource ("List projects on the Bitbucket Server / Data Center instance") and it names the filter and the return shape. It does not distinguish itself from the closely named sibling bb_get_project (single-project fetch), which an agent could plausibly confuse with this list operation.

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 implies use by saying this lists projects with an optional name filter, but gives no explicit when-to-use or when-not guidance, and does not route the agent to bb_get_project for a single project or explain when to prefer filtering by name versus paging the full list.

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