Skip to main content
Glama
Sign In
mcp-atlassian

mcp-atlassian

by SharkyND
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bitbucket_create_repository

Create a Bitbucket repository in a specified workspace or project. Configure privacy and forkability settings to match your requirements.

Instructions

Create a new repository in a workspace/project.

Args: ctx: The MCP context. workspace: Workspace name (Cloud) or project key (Server/DC). repo_slug: Repository name/slug to create. is_private: Whether the repository should be private (default: True). forkable: Whether the repository can be forked (default: False).

Returns: JSON string containing the created repository details.

Raises: ValueError: If the Bitbucket client is not configured or available.

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

Input Schema

NameRequiredDescriptionDefault
forkableNoWhether the repository can be forked
repo_slugYesRepository name/slug to create
workspaceYesWorkspace name (Cloud) or project key (Server/DC)
is_privateNoWhether the repository should be private

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses return format and a ValueError on missing client, but does not mention side effects, conflict behavior, or permission requirements beyond the basic creation. This is moderate transparency.

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?

Structured with Args/Returns/Raises sections, concise, and free of fluff. The inclusion of ctx is slightly redundant but not harmful.

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 simple create tool, the description covers purpose, parameters, returns, and a key error condition, supplemented by a rich output schema. It lacks deeper context like idempotency or permission requirements, but these are not critical for an MCP tool.

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 coverage is 100% for the four parameters, so the baseline is 3. The description duplicates schema descriptions and adds only a non-schema ctx argument, which adds marginal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create a new repository in a workspace/project' with a specific verb and resource, clearly distinguishing it from sibling tools like bitbucket_get_repository_info or bitbucket_list_repositories.

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

Usage Guidelines3/5

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

The description implies usage by defining arguments (workspace, repo_slug) but does not explicitly state when to choose this over other Bitbucket tools or mention exclusions/alternatives. It provides some context about Cloud vs Server/DC naming but no direct comparative guidance.

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