Skip to main content
Glama
Upendrasengar

bitbucket-server-mcp

manage_deployments

Manage deployments for a commit: retrieve, create, or delete deployments with key, environment, and sequence number.

Instructions

Manage deployments for a commit. Actions: "get" (retrieve a deployment), "create" (record a new deployment), "delete" (remove a deployment). GET requires key, environmentKey, and deploymentSequenceNumber. POST body requires deploymentSequenceNumber, description, displayName, environment (with displayName, key, optional type), key, state, and optional url. DELETE requires key, environmentKey, and deploymentSequenceNumber.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoDeployment key (required for get/delete). Example: "deploy-prod-1".
urlNoDeployment URL (for create, max 1024 chars).
stateNoDeployment state (for create).
actionYesOperation to perform.
projectNoProject key. Defaults to BITBUCKET_DEFAULT_PROJECT.
commitIdYesFull commit hash.
repositoryYesRepository slug.
descriptionNoDeployment description (for create, max 255 chars).
displayNameNoDeployment display name (for create, max 255 chars).
environmentKeyNoEnvironment key (required for get/delete). Example: "prod".
environmentTypeNoEnvironment type (for create).
environmentDisplayNameNoEnvironment display name (for create). Example: "Production".
deploymentSequenceNumberNoDeployment sequence number (required for get/delete). Example: 1.
Behavior4/5

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

Annotations provide no hints (readOnlyHint=false, etc.), so the description must convey behavior. It discloses that 'get' is read-only, 'create' and 'delete' are mutative. It does not mention idempotency or other traits, but the action descriptions are sufficient.

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

Conciseness4/5

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

The description is front-loaded with the main purpose and then lists actions and requirements. It is somewhat verbose but well-organized, with each sentence serving a purpose.

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

Completeness3/5

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

No output schema exists, but the description does not mention what the tool returns (e.g., deployment details for get, success status for create/delete). For a tool with 13 parameters and three actions, omitting return information leaves a gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by mapping specific parameters to actions (e.g., 'GET requires key, environmentKey, and deploymentSequenceNumber') and providing examples like 'Example: "deploy-prod-1".'

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

Purpose5/5

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

The description clearly states the tool manages deployments for a commit and lists the three actions (get, create, delete). It distinguishes itself from sibling tools, none of which focus on deployments.

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

Usage Guidelines4/5

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

The description specifies which parameters are required for each action (e.g., GET requires key, environmentKey, deploymentSequenceNumber). It does not explicitly state when not to use the tool or mention alternatives, but the action-based guidance is clear.

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

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/Upendrasengar/bitbucket-server-mcp'

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