Skip to main content
Glama
Sign In
bbkt

bbkt

by zach-snell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

manage_refs

Manage branches and tags in Bitbucket repositories: list, create, or delete branches and tags with a single tool.

Instructions

Unified tool for listing, creating, and deleting branches and tags

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": {
      "action": "<action>",
      "workspace": "<workspace>",
      "repo_slug": "<repo_slug>"
    },
    "name": "manage_refs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBranch or tag name (required for create/delete)
pageNoPage number (for list)
sortNoSort field (for list-branches)
queryNoFilter query (for list-branches)
actionYesAction to perform: 'list-branches', 'create-branch', 'delete-branch', 'list-tags', 'create-tag'
targetNoTarget commit hash (required for create-tag)
pagelenNoResults per page (for list)
repo_slugYesRepository slug
workspaceYesWorkspace slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

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 the full burden of behavioral disclosure. It mentions the operations (list, create, delete) but doesn't specify permissions required, rate limits, side effects (e.g., if deletions are permanent), or response formats. This is inadequate for a tool with multiple actions including destructive ones like delete.

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 that front-loads the core purpose without unnecessary words. It directly states the unified nature and key actions, making it easy to parse quickly.

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 tool's complexity (9 parameters, multiple actions including destructive ones), no annotations, and no output schema, the description is incomplete. It lacks behavioral details, usage context, and output information, leaving significant gaps for an agent to operate effectively.

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 parameter semantics beyond implying that actions involve branches and tags, which is already covered by the schema's action descriptions. 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 tool's purpose as a 'unified tool for listing, creating, and deleting branches and tags', which specifies the verb ('list, create, delete') and resource ('branches and tags'). However, it doesn't differentiate from sibling tools like 'manage_commits' or 'manage_repositories' that might handle related operations, so 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 any prerequisites, exclusions, or compare it to sibling tools like 'manage_source' or 'manage_repositories', leaving the agent to infer usage from the action parameter alone.

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