bitbucket-mcp-server

repositories

List Bitbucket workspace repos or fetch details for a single repo by slug to support browsing and targeted inspection.

Instructions

List repositories in a Bitbucket workspace, or get details for a single repository when repo_slug is provided.

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

Input Schema

Name	Required	Description
`page`	No	(list only) Page number or opaque next page URL
`role`	No	(list only) Filter by user role
`sort`	No	(list only) Sort by field
`pagelen`	No	(list only) Items per page (10-100, default 10)
`repo_slug`	No	Repository slug/name. If provided, returns a single repository; otherwise lists repositories.
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior3/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. "List" and "get details" imply a non-destructive read, and the mode switch is disclosed, but there is no mention of authentication needs, pagination behavior, or result volume — details that matter for an unannotated tool.

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?

One sentence, front-loaded with the primary list behavior and immediately qualified by the single-repo condition. There is no filler or redundant phrasing.

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?

With all six parameters documented in the schema and no output schema to explain, the description covers the essential decision point an agent needs. It could say more about pagination defaults and permissions, but nothing critical to a correct invocation is missing.

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% and each parameter already documents itself, including the "(list only)" markers and the workspace env-var fallback. The description restates the `repo_slug` behavior rather than adding new meaning, so the baseline of 3 applies.

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 names a concrete verb and resource ("List repositories in a Bitbucket workspace") and explicitly covers the second mode ("get details for a single repository"), so an agent knows exactly what it returns in each case. It does not explicitly contrast itself with siblings, but the resource is distinct enough that confusion is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mode switch is spelled out: supply `repo_slug` to fetch one repository, omit it to list. That is clear operational guidance for a dual-mode tool. It stops short of naming alternatives or stating exclusions (e.g., permission requirements or when to prefer a search tool), so it is not a full 5.

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

Deploy Server