Bitbucket Server MCP

get_pull_request_comment

Retrieve a specific comment from a pull request using project key, repository slug, pull request ID, and comment ID.

Instructions

Get a specific comment on a pull request.

Args: project_key: The project key. repo_slug: The repository slug. pr_id: The pull request ID. comment_id: The 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": {
      "project_key": "<project_key>",
      "repo_slug": "<repo_slug>",
      "pr_id": "<pr_id>",
      "comment_id": "<comment_id>"
    },
    "name": "get_pull_request_comment"
  }
}

Input Schema

Name	Required	Description	Default
`project_key`	Yes
`repo_slug`	Yes
`pr_id`	Yes
`comment_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0May 28, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention whether the operation is read-only, any required permissions, rate limits, or what the output format looks like. The description is minimal and lacks 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.

Conciseness3/5

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

The description is short but the argument list is redundant with the schema. While the purpose sentence is front-loaded, the parameter list does not earn its place as it adds no new information. A more concise description could omit the parameter listing entirely.

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?

Given the tool has 4 required parameters and an output schema exists (but is not described), the description fails to provide sufficient context. It does not explain the response content, pagination, or any side effects. The description is too minimal for the complexity of the tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must add meaning. However, it merely repeats the parameter names and trivial descriptions (e.g., 'The project key') that add no value beyond the schema titles. It does not explain how to obtain these identifiers or any constraints on their values.

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 states 'Get a specific comment on a pull request,' which clearly identifies the action and resource. It effectively distinguishes this tool from siblings like list_pull_request_comments (which returns all comments) and get_pull_request (which returns the PR itself).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this tool is for retrieving a single comment by ID, while list_pull_request_comments should be used to fetch all comments on a PR.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server