bitbucket-mcp-server

commits

List recent repository history or retrieve details for a specific commit by providing its hash.

Instructions

List recent commits for a repository, or get details for a single commit when commit_hash is provided.

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

Input Schema

Name	Required	Description
`page`	No	(list only) Page number or opaque next page URL
`branch`	No	(list only) Branch name (defaults to main branch)
`pagelen`	No	(list only) Items per page (10-100, default 10)
`repo_slug`	Yes	Repository slug/name
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.
`commit_hash`	No	Commit hash. If provided, returns single commit details; otherwise lists recent commits.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full load. It does disclose the key behavioral branch (single-commit detail versus recent-commit list) and the word 'recent' hints at ordering, but it says nothing about pagination behavior, result volume, permissions, or what a list entry contains. The mode switching is genuine added value, but the disclosure is thin for a tool with zero annotation coverage.

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?

A single sentence, front-loaded with the primary use and immediately qualified by the conditional alternative. There is no redundant or filler wording.

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 read-only list/detail tool with full schema coverage and no output schema, the description covers both invocation modes an agent must choose between. The main remaining gap is that return shape must be inferred, but that is minor given how much the schema already carries.

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 all six parameters, including the '(list only)' qualifiers and the workspace env-var fallback, are already documented in the schema. The description only restates the `commit_hash` conditional, adding no format, default, or constraint detail beyond the schema. 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?

The description names a specific verb and resource ('List recent commits for a repository') and explicitly splits it into two modes: listing versus single-commit detail. It does not differentiate itself from siblings such as list-branches, but the dual-mode purpose is unambiguous.

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?

It implies the selection rule the agent needs — supply `commit_hash` for details, omit it to list — which is the core usage decision. There is no explicit guidance about when this tool is preferable to sibling tools, nor any exclusions or prerequisites.

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

Deploy Server