Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

List commits

bb_list_commits

List repository commits or a commit range using since/until, with optional client-side author filtering by username or email.

Instructions

List commits of a repository (or a range with since/until). Optional client-side author filter on username or email — paging metadata reflects unfiltered pages.

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>",
      "repositorySlug": "<repositorySlug>"
    },
    "name": "bb_list_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number (Cloud only; from nextPageStart of the previous call). Ignored on Server/DC.
limitNoPage size (1-1000).
sinceNoExclude commits reachable from this branch/tag/commit (Server/DC only).
startNoZero-based page offset (Server/DC).
untilNoEnd of the commit range (default: default branch head).
authorNoFilter by author username or email (client-side, case-insensitive contains).
projectKeyYesProject key.
includeMergesNoInclude merge commits (Cloud: filtered client-side).
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the one real footgun: the author filter is applied client-side, so paging metadata reflects unfiltered pages — an agent that assumes server-side filtering would mis-paginate. It does not mention that this is a read-only operation, required repository access permissions, or platform (Cloud vs Server/DC) behavior, though the schema covers the latter.

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?

Two sentences, no waste, and the primary resource listing is front-loaded ahead of the qualifier and the caveat. Every clause carries information an agent needs.

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?

For a 9-parameter read tool with no annotations and no output schema, the description covers the purpose, the range usage, and the most consequential behavioral quirk. The remaining gap is return shape — with no output schema the description never says what a commit entry contains or how results are ordered — which is a real but modest omission.

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 coverage is 100%, so all nine parameters including author, since, until, and the Cloud/Server paging split are already documented in the schema. The description restates the author filter's client-side nature and adds the paging-metadata caveat, which is marginal added value over an already complete schema — baseline 3 is appropriate.

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 ('List commits of a repository') and adds the range variant with since/until. It does not need to differentiate against a sibling commit-listing tool since none exists, but it also does not contrast itself with adjacent tools like bb_browse_repository or bb_get_file_content, which is the only thing keeping it from a 5.

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?

Usage is implied rather than stated: the parenthetical '(or a range with since/until)' tells the agent when the range form applies, but there is no explicit when-to-use / when-not-to-use guidance or named alternative. A call to bb_list_commits versus browsing history another way is left to inference.

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