Skip to main content
Glama
enesjakozh
Kallows

MCP Bitbucket Python

by Kallows
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

bb_delete_issue

Remove an issue from a Bitbucket repository by specifying its ID and repository slug. Supports workspace customization for targeted issue management in Python-based Bitbucket integration.

Instructions

Delete an issue from a Bitbucket repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesID of the issue to delete
repo_slugYesRepository slug/name
workspaceNoRepository workspace (defaults to kallows)kallows

Implementation Reference

  • src/mcp_bitbucket/server.py:736-754 (handler)
    Handler logic that deletes the specified issue in a Bitbucket repository by sending a DELETE request to the Bitbucket API issues endpoint. Handles success (204) and error cases.
    elif name == "bb_delete_issue":
    workspace = arguments.get("workspace", "kallows")
    repo_slug = arguments.get("repo_slug")
    issue_id = arguments.get("issue_id")

    url = f"https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/issues/{issue_id}"
    response = requests.delete(url, auth=auth, headers=headers)

    if response.status_code == 204:
        return [types.TextContent(
            type="text",
            text=f"Issue {issue_id} deleted successfully"
        )]
    else:
        return [types.TextContent(
            type="text",
            text=f"Failed to delete issue: {response.status_code}\n{format_permission_error(response.text)}",
            isError=True
        )]
  • src/mcp_bitbucket/server.py:271-293 (registration)
    Tool registration including name, description, and input schema definition within the list_tools handler.
    types.Tool(
    name="bb_delete_issue",
    description="Delete an issue from a Bitbucket repository",
    inputSchema={
        "type": "object",
        "properties": {
            "workspace": {
                "type": "string",
                "description": "Repository workspace (defaults to kallows)",
                "default": "kallows"
            },
            "repo_slug": {
                "type": "string",
                "description": "Repository slug/name"
            },
            "issue_id": {
                "type": "string",
                "description": "ID of the issue to delete"
            }
        },
        "required": ["repo_slug", "issue_id"]
    }
),
  • src/mcp_bitbucket/server.py:271-293 (schema)
    Input schema defining parameters for the bb_delete_issue tool: workspace (optional), repo_slug, and issue_id (required).
    types.Tool(
    name="bb_delete_issue",
    description="Delete an issue from a Bitbucket repository",
    inputSchema={
        "type": "object",
        "properties": {
            "workspace": {
                "type": "string",
                "description": "Repository workspace (defaults to kallows)",
                "default": "kallows"
            },
            "repo_slug": {
                "type": "string",
                "description": "Repository slug/name"
            },
            "issue_id": {
                "type": "string",
                "description": "ID of the issue to delete"
            }
        },
        "required": ["repo_slug", "issue_id"]
    }
),

Tool Definition Quality

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 for behavioral disclosure. While 'Delete' implies a destructive mutation, it doesn't specify whether this action is reversible, what permissions are required, if there are confirmation prompts, rate limits, or what happens to associated data (e.g., comments). This leaves significant gaps for a destructive operation.

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, efficient sentence with zero waste. It's appropriately sized for a straightforward deletion tool and front-loads the core purpose immediately.

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 destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't cover behavioral aspects like permissions, irreversibility, or error conditions, nor does it explain what happens upon successful deletion. Given the complexity and risk of deletion operations, more context is needed.

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 all parameters are documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema (e.g., explaining relationships between parameters or usage patterns). Baseline 3 is appropriate when 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 ('Delete') and resource ('an issue from a Bitbucket repository'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling deletion tools like 'bb_delete_file' or 'bb_delete_repository', which would require mentioning it's specifically for issues rather than files or entire repositories.

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., needing appropriate permissions), when not to use it (e.g., for archiving instead of deletion), or refer to sibling tools like 'bb_create_issue' for context on issue lifecycle management.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kallows/mcp-bitbucket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server