Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

List repositories in a project

bb_get_repositories

Lists a Bitbucket project's repositories as compact cards with slug, name, description, and visibility. Supports optional name filtering and returns pagination metadata.

Instructions

List repositories of a project as compact cards (slug, name, description, visibility). Optional server-side name filter. Returns paging metadata.

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": {
      "projectKey": "<projectKey>"
    },
    "name": "bb_get_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter repositories by name (server-side 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).
projectKeyYesProject key (on Cloud: workspace slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it discloses the compact return shape and that paging metadata is returned, which is genuinely useful. However, it omits access/permission requirements, behavior when projectKey is invalid or empty, and any pagination-iteration guidance beyond one mention. Notably 'server-side name filter' is an oversimplification the schema contradicts (client-side on Cloud), though the schema corrects it.

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 short sentences, front-loaded with the resource and return shape, followed by the filter and the paging note. No filler or repetition; every sentence adds a distinct fact.

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 five-parameter read-only listing with no output schema and no annotations, the description states the core purpose, the returned fields, the filter, and the presence of paging. Missing pieces are peripheral (permission requirements, empty-result behavior, how to advance pages), so it is close to complete but not exhaustive.

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 projectKey, name, page, limit, and start including the Cloud/Server-DC split. The description adds essentially nothing beyond what the schema states, so the baseline 3 applies; the 'server-side' phrasing slightly mischaracterizes the name parameter 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?

The description opens with a specific verb+resource+scope ('List repositories of a project') and enumerates the returned card fields (slug, name, description, visibility), so an agent knows exactly what it gets. It doesn't explicitly distinguish itself from siblings like bb_get_repository (singular lookup) or bb_browse_repository, leaving that differentiation to inference.

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?

There is no explicit when-to-use or when-not guidance, and no alternative tool is named. The phrase 'Optional server-side name filter' hints at a filtered-listing use case, but the agent must infer that bb_get_repository is the right choice for a single repo and this one for enumeration.

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