Bitbucket Cloud MCP Server

create_repository

Create a new repository in a Bitbucket Cloud workspace with configurable settings for privacy, language, issue tracking, and project assignment.

Instructions

Create a new repository in the specified workspace.

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>",
      "repo_slug": "<repo_slug>"
    },
    "name": "create_repository"
  }
}

Input Schema

Name	Required	Description
`workspace`	Yes	The workspace slug
`repo_slug`	Yes	The repository slug
`name`	No	Repository name
`description`	No	Repository description
`is_private`	No	Whether the repository is private
`language`	No	Primary language
`has_issues`	No	Enable issue tracker
`has_wiki`	No	Enable wiki
`project_key`	No	Project key to add repo to

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 29, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as required permissions, whether creation is idempotent, rate limits, error conditions, or what happens on success (e.g., returns a repository object). This leaves significant gaps for a mutation 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?

The description is a single, clear sentence with zero waste. It's front-loaded with the core action and resource, making it efficient and easy to parse.

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?

For a creation tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It lacks context on permissions, behavioral details, and expected outcomes, which are crucial for safe and effective use by an AI agent.

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 fully documents all 9 parameters. The description adds no additional meaning beyond implying a 'workspace' parameter, which is already covered. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Create') and resource ('new repository in the specified workspace'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_branch' or 'create_issue' beyond the resource type, which is why it doesn't reach the highest 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 (e.g., workspace permissions), when not to use it, or how it relates to siblings like 'get_repository' or 'list_repositories' for checking existing repos first.

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