Skip to main content
Glama
tugudush
by tugudush

bb_get_diff

Retrieve raw unified diffs for a commit against its parent or between two commits, with optional path filtering and whitespace handling.

Instructions

Get the raw unified diff between commits. Use a single commit hash to diff against its parent, or "commit1..commit2" for comparing two commits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFilter diff to a single file path
specYesCommit spec: a single commit hash (diffs against parent), or two commits as "commit1..commit2"
topicNoWhen true with two-commit spec, produces a 3-dot diff (source vs merge-base)
filterNoJMESPath expression to filter/transform structured response data. Applied before format conversion. Example: "values[].{name: full_name, lang: language}" — see https://jmespath.org for syntax
contextNoNumber of context lines around changes
repo_slugYesThe repository name
workspaceYesThe workspace or username
output_formatNoResponse format: "text" (default, human-readable), "json" (structured JSON), or "toon" (Token-Oriented Object Notation — compact tabular format that reduces LLM token consumption by 30-60%)
ignore_whitespaceNoIgnore whitespace changes
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 only states the action and spec format, but does not disclose read-only status, pagination behavior, error handling, or the nature of the output beyond 'raw unified diff'. This is minimal behavioral disclosure.

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 concise with two sentences, immediately states the core function, and provides essential spec examples without unnecessary filler. Excellent structure and front-loading.

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 a rich schema covering 9 parameters and all descriptions, the description focuses effectively on the key spec parameter. It does not cover the filter, topic, or output_format options, but these are well-documented in the schema, so the description is adequate for the overall context.

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 descriptions cover 100% of the 9 parameters, so the description adds little beyond repeating the spec semantics already present. The description's mention of spec usage mirrors the schema's description, thus the baseline 3 applies.

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 the raw unified diff between commits' with a specific verb, resource, and output format. It distinguishes itself from sibling tools like bb_get_pull_request_diff by focusing on commit-to-commit comparisons, and the spec syntax is explicitly clarified.

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?

Provides explicit usage instructions for the spec parameter: single commit hash for parent diff, or 'commit1..commit2' for comparing two commits. While it doesn't name alternative tools, the context for when to use this tool is clear.

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

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