Skip to main content
Glama
Sign In
Bitbucket MCP Server

Bitbucket MCP Server

by ATERCATES
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

listRepositories

Lists Bitbucket repositories in a workspace, with optional name filtering, pagination, and automatic retrieval of up to 1000 items for comprehensive discovery.

Instructions

List Bitbucket repositories

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

Input Schema

NameRequiredDescriptionDefault
allNoWhen true (and no page is provided), automatically follows Bitbucket next links to return all items up to 1000.
nameNoFilter repositories by name (partial match supported)
pageNoBitbucket page number to fetch (1-based).
limitNoDeprecated alias for pagelen. Use pagelen/page/all for pagination control.
pagelenNoNumber of items per page (Bitbucket pagelen). Defaults to 10 and caps at 100.
workspaceNoBitbucket workspace name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

C2.9/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 full burden. It does not disclose that results are paginated, the existence of the 'all' parameter for auto-fetch, or the rate limit behavior. The minimal description fails to communicate important behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, which is efficient. However, it lacks structure: critical information like pagination and filtering is not front-loaded. It is not overly verbose but could be more informative without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description should explain what the tool returns and how pagination works. It does not describe the return format, the behavior of the 'all' parameter, or how to handle large result sets. This is inadequate for a list tool with 6 parameters and many sibling tools.

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 baseline is 3. The description adds no semantic value beyond the schema; it does not explain parameter interactions (e.g., using 'all' with pagination) or provide context for optional parameters.

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 states 'List Bitbucket repositories' which clearly indicates the verb and resource. It distinguishes from sibling tools like getRepository (single repo) and listWorkspaces (workspaces), but does not specify the scope (e.g., across workspaces) or whether it returns full details or just names.

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?

No guidance on when to use this tool versus alternatives such as getRepository for a single repo or listBranches for a specific repository. No exclusions or prerequisites mentioned.

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