Skip to main content
Glama
Sign In
bitbucket-mcp-server

bitbucket-mcp-server

by WilliamLINWEN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-pr-description

Update a Bitbucket pull request's title and/or description to correct or clarify its details.

Instructions

Update the title and/or description of a pull request

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": {
      "repo_slug": "<repo_slug>",
      "pull_request_id": "<pull_request_id>"
    },
    "name": "update-pr-description"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title for the pull request
repo_slugYesRepository slug/name
workspaceNoBitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
descriptionNoNew description for the pull request
pull_request_idYesPull request ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. Other than the phrase 'title and/or description', which hints that fields are optional, it does not say whether this is a full overwrite, what permissions are required, whether existing values are preserved when omitted, or what a successful response looks like.

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?

A single clean sentence with zero wasted wording, and the verb and resource are front-loaded. It is arguably too terse for a mutation tool, but there is no padding or redundancy.

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?

For a write operation with no annotations and no output schema, the description should cover at least partial-update semantics and permission expectations. With five parameters and mutation behavior, the one-line description leaves material gaps for an agent to call it confidently.

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 all five parameters are already documented in the schema, including the workspace env-var fallback. The description only restates that title and description are the updatable fields, adding nothing the schema does not already provide.

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 names a specific verb (update) and resource (pull request title/description), which is unambiguous and matches the tool name. It does not distinguish itself from any sibling, but no sibling appears to overlap this operation, so differentiation is not critical.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g., required permissions or branch state), and no mention of alternatives. The narrow scope of the operation implies its usage, but the description never states it.

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