Skip to main content
Glama
jlromano

Bitbucket MCP Server

by jlromano

list_workspaces

Retrieve all accessible Bitbucket workspaces to organize and manage repositories effectively.

Instructions

List all available Bitbucket workspaces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the logic for listing workspaces.
    async listWorkspaces(): Promise<any[]> {
      const response = await this.api.get('/workspaces');
      return response.data.values;
    }
  • src/index.ts:45-52 (registration)
    Tool definition registration for list_workspaces.
    {
      name: 'list_workspaces',
      description: 'List all available Bitbucket workspaces',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The request handler case that calls the BitbucketClient to list workspaces.
    case 'list_workspaces': {
      const workspaces = await client.listWorkspaces();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(workspaces, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List all available') but doesn't cover critical aspects like pagination, rate limits, authentication needs, or what 'available' means (e.g., accessible to the user). This leaves significant gaps for a tool that likely interacts with an API.

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, direct sentence with no wasted words. It front-loads the key information ('List all available Bitbucket workspaces'), making it highly efficient and easy to parse.

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?

Given the tool's simplicity (zero parameters, no output schema), the description is minimally adequate but lacks depth. Without annotations or output schema, it should ideally mention what the list returns (e.g., workspace names, IDs) or behavioral constraints, but it doesn't, leaving the agent with incomplete context for a read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, so it meets expectations by not adding unnecessary details. A baseline of 4 is appropriate for a zero-parameter tool.

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?

The description clearly states the tool's purpose with a specific verb ('List') and resource ('Bitbucket workspaces'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'list_repositories' or 'list_branches' beyond specifying the resource type, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or comparisons to sibling tools like 'list_repositories' (which might list repositories within a workspace), leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jlromano/bitbucket-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server