Skip to main content
Glama
MCP Dokploy Online
by igoruam

bitbucket-getBitbucketBranches

Read-onlyIdempotent

Fetch Bitbucket branches for a specified owner and repository to review available branches for deployment or configuration tasks.

Instructions

GET /bitbucket.getBitbucketBranches

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "bitbucket-getBitbucketBranches"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes
bitbucketIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and idempotency are covered structurally. The description adds no behavioral context at all — no mention of pagination, rate limits, auth requirements, or whether a missing repo yields an error or an empty list — and the "GET" prefix merely echoes the readOnly annotation.

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

Conciseness2/5

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

It is a single token-efficient line, but that brevity comes from under-specification rather than tight writing; there is no front-loaded statement of purpose for the reader to anchor on.

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

Completeness1/5

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

A three-parameter, open-world network call with no output schema and no documentation of any parameter is far from self-describing. Nothing in the definition tells an agent how to construct a valid call or what to expect back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are three parameters (owner, repo, bitbucketId), none of which are explained in either the schema or the description. The critical ambiguity — whether bitbucketId is a provider connection id and whether it is optional — is left entirely unaddressed.

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

Purpose2/5

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

The description is essentially the tool name re-rendered as a route: "GET /bitbucket.getBitbucketBranches". The GET verb implies retrieval and the name implies branches, but the description never states what is returned (a list of branches for a repo) or its scope, and it does nothing to distinguish itself from the sibling github/gitea/gitlab branch tools.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no preconditions, and no mention of alternatives such as the equivalent GitHub, Gitea, or GitLab branch tools listed as siblings. An agent must infer everything from the tool name 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