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

bitbucket-mcp-server

by WilliamLINWEN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create-pr-comment

Posts a comment on a Bitbucket pull request or replies to an existing comment by parent ID, including optional inline file and line references.

Instructions

Create a comment on a pull request, or reply to an existing comment by specifying a parent comment ID

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>",
      "content": "<content>"
    },
    "name": "create-pr-comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesComment content in plain text
to_lineNoLine number in the new version of the file (for inline comments)
file_pathNoPath to the file for inline comments
from_lineNoLine number in the old version of the file (for inline comments)
parent_idNoID of the parent comment to reply to
repo_slugYesRepository slug/name
workspaceNoBitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
pull_request_idYesPull request ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.3/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, and it discloses very little. It does not say whether inline comments require file_path plus from_line/to_line, what happens on success, whether the comment triggers notifications, or what authorization is needed for a write operation.

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 front-loaded sentence that names the primary action first and the variant second, with no filler. It is efficient, though for an eight-parameter mutation tool it is arguably thinner than the complexity warrants.

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

Completeness4/5

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

Placeholder.

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 every parameter including parent_id, file_path, to_line, and workspace fallback is already documented in the schema. The description's mention of parent comment ID only restates what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a comment on a pull request') and adds a second mode ('reply to an existing comment'). An agent can distinguish it from listing siblings like pr-comments or resolve-pr-comment, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The reply mode is described with its trigger ('by specifying a parent comment ID'), which implicitly tells the agent how to choose between a new comment and a reply. However, there is no explicit when-not guidance, no mention of prerequisites such as permissions, and no named alternatives.

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