Skip to main content
Glama

Get Commits

bitbucket_get_commits
Read-onlyIdempotent

Retrieve commits from a Bitbucket repository with filters for date range, file path, and pagination. Lists commits in reverse chronological order.

Instructions

Get commits for a repository.

Lists commits in reverse chronological order. Use since/until to specify a commit range (like git log since..until). Use path to only show commits that modified a specific file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFilter commits affecting this file path
limitNoMax results (1-100)
sinceNoCommit hash or ref — exclude commits reachable from this
startNoPagination start index
untilNoCommit hash or ref — include commits reachable from this (default: default branch HEAD)
project_keyYesThe project key
repository_slugYesThe repository slug
response_formatNoOutput format: markdown (default) or jsonmarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds behavioral context by explaining the reverse chronological order and the semantics of 'since' and 'until' (like git log). This goes beyond the annotations without contradicting them.

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 only three sentences with no wasted words. It is front-loaded with the main purpose, then provides key usage details. Every sentence contributes meaning without redundancy.

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 the tool has 8 parameters, a complete output schema, and minor annotations, the description adequately covers the core functionality (ordering, filtering by range or path). It does not mention pagination or limit/start, but those are documented in the schema. The description is sufficient for an agent to understand the tool's primary use.

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?

The input schema has 100% description coverage for all 8 parameters. The description adds value by explaining the intended usage of 'since', 'until', and 'path' with a git-log analogy, which is not present in the schema, thus enhancing parameter semantics beyond the 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 'Get commits for a repository' as the overall purpose, and specifies the reverse chronological order. This distinguishes it from sibling tools like bitbucket_get_commit (single commit) and bitbucket_get_commit_diff (diff). The verb 'get' and resource 'commits' are specific and unambiguous.

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 provides explicit guidance for using 'since' and 'until' to specify a commit range and 'path' to filter by file, including a git-log analogy. However, it does not explicitly contrast with sibling tools like bitbucket_get_commit or bitbucket_get_commit_diff, though the context implies differentiation.

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/christopherekfeldt/mcp-bitbucket-dc'

If you have feedback or need assistance with the MCP directory API, please join our Discord server