Skip to main content
Glama
Upendrasengar

bitbucket-server-mcp

manage_comment

Manage pull request comments: create, edit, delete, and add or remove emoji reactions. Supports inline, threaded, and task comments with thread resolution.

Instructions

Manage pull request comments. Actions: "create" (general, inline, threaded, or tasks), "edit" (update text/severity/state/threadResolved), "delete", "react" (add emoji reaction), "unreact" (remove reaction). state: RESOLVED toggles the task checkbox on a BLOCKER comment; threadResolved: true closes the conversation (the "Resolve" button in the UI). They are independent and can be passed together.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineNoLine number for inline comments (create only).
prIdYesPull request ID.
textNoComment text (required for create and edit).
stateNoComment state. PENDING = draft (create only). RESOLVED = mark as resolved (edit only). OPEN = reopen (edit only).
actionYesOperation to perform on the comment.
projectNoProject key. Defaults to BITBUCKET_DEFAULT_PROJECT.
versionNoComment version for optimistic locking (required for edit and delete).
diffTypeNoWhich diff to anchor the comment on. EFFECTIVE = overall PR diff (default). COMMIT = a single commit's diff. RANGE = diff between two specific commits.
emoticonNoEmoticon shortcut for react/unreact (e.g. thumbsup, heart, tada). Use search_emoticons to find available options.
filePathNoFile path for inline comments (create only).
fileTypeNoWhich side of the diff. TO = new version (default). FROM = old version (useful for renames).
lineTypeNoType of line being commented on. ADDED = new line, REMOVED = deleted line, CONTEXT = unchanged line visible in the diff.
parentIdNoParent comment ID for threaded replies (create only).
severityNoComment severity. BLOCKER marks it as a task (create and edit).
commentIdNoComment ID (required for edit, delete, react, unreact).
repositoryYesRepository slug.
threadResolvedNoClose or reopen the comment thread (edit only). Independent of `state`. Requires Bitbucket Data Center >= 8.9; older servers accept the PUT but ignore the field.
Behavior4/5

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

Annotations don't provide behavioral details, but the description discloses important traits: optimistic locking via version, independence of state and threadResolved, and the Bitbucket Data Center requirement for threadResolved. This adds significant value beyond annotations.

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 relatively concise, combining paragraph and bullet-like structure for actions. It could be more structured (e.g., separate sections for actions and behaviors), but every sentence adds value.

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?

Given 17 parameters, no output schema, and many enums, the description covers main behaviors and parameter constraints. It lacks return value details but is complete enough for an agent to invoke correctly.

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 description coverage is 100%, so baseline is 3. The description adds meaning by explaining the interaction between state and threadResolved, the meaning of RESOLVED vs threadResolved, and that version is required for edit/delete. This extends beyond schema.

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 pull request comments with specific actions (create, edit, delete, react, unreact) and explains key behaviors like state and threadResolved. It distinguishes itself from siblings by focusing on PR comments, not commit comments.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., manage_commit_comments). It provides context for actions but lacks when-not-to-use or comparisons to sibling tools.

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