Skip to main content
Glama
MCP Dokploy Online
by igoruam

bitbucket-update

Idempotent

Update an existing Bitbucket git provider in Dokploy, including its name, workspace, organization, and authentication credentials such as app password, API token, username, and email.

Instructions

POST /bitbucket.update

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": {
      "bitbucketId": "<bitbucketId>",
      "gitProviderId": "<gitProviderId>",
      "name": "<name>"
    },
    "name": "bitbucket-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
apiTokenNo
appPasswordNo
bitbucketIdYes
gitProviderIdYes
bitbucketEmailNo
organizationIdNo
bitbucketUsernameNo
bitbucketWorkspaceNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply idempotentHint and openWorldHint, but the description adds nothing beyond them — no note on whether existing credentials are overwritten, whether omitted fields are preserved, or what permissions are required. It does not contradict the annotations, but it carries zero behavioral weight.

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 short, but that is under-specification rather than conciseness: a single route fragment with no informative content. Nothing is front-loaded because there is nothing to front-load.

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?

For a 9-parameter mutation with no output schema and no description coverage, this is wholly inadequate. An agent cannot determine required auth mode, update semantics, or side effects from the definition.

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?

The schema has 9 parameters at 0% description coverage, and the description mentions none of them. Critical ambiguities — apiToken vs appPassword vs bitbucketEmail/username auth modes, and whether gitProviderId/organizationId are reassignable — are left entirely unresolved.

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?

"POST /bitbucket.update" only restates the tool name with an HTTP verb. It does not say what a Bitbucket connection is being updated, what fields matter, or how it differs from siblings such as bitbucket-create or github-update.

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 prerequisites, and no indication of when to prefer this over bitbucket-create or the sibling provider-update tools. An agent must guess entirely from the name.

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