Bitbucket Cloud MCP Server

list_repositories

Retrieve and filter repositories from a Bitbucket Cloud workspace with paginated results, sorting, and role-based access.

Instructions

List repositories in a workspace. Returns paginated results with repository details.

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": {
      "workspace": "<workspace>"
    },
    "name": "list_repositories"
  }
}

Input Schema

Name	Required	Description
`workspace`	Yes	The workspace slug
`role`	No	Filter by role
`q`	No	Query string for filtering
`sort`	No	Sort field (e.g., "-updated_on")
`page`	No	Page number
`pagelen`	No	Results per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 29, 2025

TDQS

B3.3/5.0

Behavior3/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 usefully adds that results are paginated, which isn't obvious from the schema alone. However, it doesn't describe authentication requirements, rate limits, error conditions, or what 'repository details' specifically includes. For a read operation with 6 parameters, more behavioral context would be helpful.

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 perfectly concise at two sentences. The first sentence states the core purpose, and the second adds critical behavioral context about pagination. Every word earns its place with zero redundancy or unnecessary elaboration.

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 read-only list operation with good schema coverage but no output schema, the description provides adequate but minimal context. It covers the basic purpose and pagination behavior, but lacks details about authentication, error handling, or what specific repository details are returned. Given the 6 parameters and no annotations, more completeness would be beneficial.

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 schema already documents all 6 parameters thoroughly. The description adds no additional parameter semantics beyond mentioning pagination (implied by page/pagelen parameters) and filtering (implied by role/q parameters). This meets the baseline expectation when schema coverage is complete.

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 action ('List repositories') and resource ('in a workspace'), making the purpose immediately understandable. It distinguishes itself from other list operations like list_branches or list_issues by specifying repositories. However, it doesn't explicitly differentiate from list_repository_forks, which is a similar but distinct operation.

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 when to choose list_repositories over get_repository (for single repo details) or list_repository_forks (for fork-specific listings). No context about prerequisites, typical use cases, or exclusions is provided.

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