Bitbucket MCP Server

list_pr_commits

List commits on a Bitbucket pull request with pagination support. Enter the project key, repository slug, and pull request ID to retrieve the commit history.

Instructions

List commits on a specific pull request with pagination

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": {
      "projectKey": "<projectKey>",
      "repoSlug": "<repoSlug>",
      "pullRequestId": "<pullRequestId>"
    },
    "name": "list_pr_commits"
  }
}

Input Schema

Name	Required	Description
`repoSlug`	Yes	The repository slug
`projectKey`	Yes	The project key (e.g., PROJ)
`max_results`	No	Maximum number of commits to return (default: 100)
`pullRequestId`	Yes	The pull request ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Jul 15, 2026

TDQS

A3.6/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 burden. It mentions pagination but provides no details on ordering, whether all commits are returned or just the first page, or the format of the response. For a tool with no annotations, more behavioral context is expected.

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

Conciseness5/5

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

The description is a single, focused sentence with no extraneous words. It efficiently conveys the essential purpose and key feature (pagination). Every word earns its place.

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 no annotations, no output schema, and the existence of many sibling tools, the description lacks completeness. It does not specify return format, ordering, error handling, or how pagination works (e.g., cursor vs offset). For a list operation, this leaves gaps for an agent to correctly process the output.

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?

All 4 parameters have descriptions in the input schema, covering 100% of their semantics. The tool description adds no additional meaning beyond 'with pagination', which is already captured by the max_results parameter. Baseline 3 is appropriate as the schema handles the details.

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 explicitly states the verb 'list' and the resource 'commits on a specific pull request' with pagination. It clearly distinguishes from siblings like get_repo_commits (list commits on a branch) and get_commit_detail (single commit), making the purpose very specific.

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 indicates the tool is for listing commits on a pull request with pagination, which implies its primary use case. However, it does not explicitly mention when not to use it or compare it to alternatives such as get_repo_commits for branch commits. Still, the context is clear enough for basic selection.

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