Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get file content

bb_get_file_content

Fetch raw file content from a Bitbucket repository at a branch, tag, or commit, with long files truncated and stats returned for safe inspection.

Instructions

Fetch the raw content of a file from a repository (optionally at a specific branch/tag/commit). Long files are truncated with statistics.

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

Input Schema

NameRequiredDescriptionDefault
atNoBranch, tag or commit to read from.
pathYesFile path, e.g. 'src/index.ts'.
maxCharsNoMaximum returned characters; the rest is truncated.
projectKeyYesProject key.
repositorySlugYesRepository slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add one genuinely useful trait — that long output is truncated and statistics are returned — but says nothing about missing-file behavior, binary or encoding handling, or permission requirements, leaving most behavioral questions unanswered.

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

Conciseness4/5

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

A single tight sentence with the resource and the optional revision qualifier front-loaded. The truncation caveat is appended in a second short sentence and earns its place; no filler.

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 simple five-parameter read tool with no output schema and no annotations, the description covers what is fetched, the optional revision, and the truncation behavior of the return value. Error and encoding behavior are the notable omissions.

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 five parameters, including the byte limits on maxChars and the branch/tag/commit semantics of 'at', are already documented. The description adds only the link between truncation and maxChars, which the schema already implies.

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 ('Fetch the raw content of a file from a repository') and scopes it with an optional revision. It is distinguishable from directory-browsing or code-searching siblings by the phrase 'raw content of a file', though no sibling is named explicitly.

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: an agent can infer this is the tool for reading a known file path. There is no explicit when-to-use versus bb_browse_repository or bb_search_code, and no guidance on prerequisites or failure modes for a wrong path or revision.

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