Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveBitbucketProvider

Idempotent

Save a Bitbucket provider configuration for a Dokploy application, linking repository details, branch, and build settings so deployments can use the selected Bitbucket source.

Instructions

POST /application.saveBitbucketProvider

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": {
      "bitbucketBuildPath": "<bitbucketBuildPath>",
      "bitbucketOwner": "<bitbucketOwner>",
      "bitbucketRepository": "<bitbucketRepository>",
      "bitbucketRepositorySlug": "<bitbucketRepositorySlug>",
      "bitbucketId": "<bitbucketId>",
      "applicationId": "<applicationId>",
      "bitbucketBranch": "<bitbucketBranch>"
    },
    "name": "application-saveBitbucketProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchPathsNo
bitbucketIdYes
applicationIdYes
bitbucketOwnerYes
bitbucketBranchYes
enableSubmodulesNo
bitbucketBuildPathYes
bitbucketRepositoryYes
bitbucketRepositorySlugYes

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 already declare idempotentHint=true and openWorldHint=true, so the bar is lower, but the description adds nothing: not whether an existing provider is overwritten, what happens to unlisted fields, or what authorization is needed. The route text duplicates the name and provides no behavioral context.

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 short line, but that brevity reflects under-specification rather than economical writing. There is no front-loaded purpose statement an agent could act 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?

For a 9-parameter mutation with no output schema and only minimal annotations, the definition is wholly inadequate: nothing tells the agent what data must be gathered beforehand or what a successful save returns.

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?

With 9 parameters (7 required) and 0% schema description coverage, the description must compensate for undocumented fields like watchPaths, enableSubmodules, and bitbucketBuildPath. It mentions none of them, leaving all parameter meaning to bare property names and types.

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 only the HTTP route "POST /application.saveBitbucketProvider", which restates the tool name rather than explaining what saving a Bitbucket provider does. It conveys the write verb and the resource only implicitly through the name; nothing distinguishes it from the many sibling save*Provider 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 prerequisites, and no mention of alternatives such as application-saveGithubProvider or bitbucket-update. The agent must infer everything from the 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