Skip to main content
Glama
Sign In
Bitbucket MCP Server

Bitbucket MCP Server

by ATERCATES
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

listWorkspaces

Retrieve Bitbucket workspaces the user can access. Supports pagination and an option to fetch up to 1000 items.

Instructions

List Bitbucket workspaces the user has access to

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

Input Schema

NameRequiredDescriptionDefault
allNoWhen true (and no page is provided), automatically follows Bitbucket next links to return all items up to 1000.
pageNoBitbucket page number to fetch (1-based).
pagelenNoNumber of items per page (Bitbucket pagelen). Defaults to 10 and caps at 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the burden. It only states the basic function without disclosing traits like pagination behavior, read-only nature, or that it may return many results. The schema reveals pagination params, but the description does not reference them.

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?

Single clear sentence with no wasted words; front-loaded with the essential purpose.

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 simple list tool with no output schema, the description is adequate but could benefit from mentioning response structure or pagination behavior to be fully self-contained.

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%, so baseline is 3. The description adds no extra meaning to the parameters (pagelen, page, all) beyond what the schema already provides.

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 Bitbucket workspaces the user has access to' clearly states the action (list) and resource (workspaces), distinguishing it from sibling tools that focus on repositories, pull requests, or other entities.

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?

No explicit guidance on when to use this tool vs alternatives, but it is the only workspace listing tool among siblings, so usage is implied. Missing when-not or conditions like authentication requirements.

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