mcp-bitbucket-dc

Get File Content

bitbucket_get_file_content

Read-onlyIdempotent

Retrieve raw text content of any file from a Bitbucket Data Center repository, optionally at a specific branch, tag, or commit.

Instructions

Get the raw content of a file from a repository.

Returns the full file content as text. Use at to fetch from a specific branch, tag, or commit hash.

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": {
      "project_key": "<project_key>",
      "repository_slug": "<repository_slug>",
      "path": "<path>"
    },
    "name": "bitbucket_get_file_content"
  }
}

Input Schema

Name	Required	Description	Default
`at`	No	Branch, tag, or commit (default: default branch)
`path`	Yes	File path (e.g. 'src/main/App.java')
`project_key`	Yes	The project key
`repository_slug`	Yes	The repository slug
`response_format`	No	Output format: markdown (default) or json	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Apr 30, 2026

addedInput schema / properties / response_format

Added value: +{
+  "default": "markdown",
+  "description": "Output format: markdown (default) or json",
+  "enum": [
+    "markdown",
+    "json"
+  ],
+  "type": "string"
+}

First observedv0.1.0Feb 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds that it returns 'full file content as text', but does not disclose additional behavioral traits like auth requirements, rate limits, or handling of binary files.

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?

Three concise sentences, no redundancy. Front-loaded purpose, then return format, then parameter hint. Every sentence earns its place.

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 read tool with output schema, the description is complete. It covers purpose, output, and key parameter. No missing context like error handling, but output schema likely handles that.

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?

Input schema covers 100% of parameters with descriptions. The description reinforces the 'at' parameter usage but adds no significant meaning beyond the schema. Baseline is 3 for high coverage.

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 content of a file from a repository' with a specific verb and resource. It distinguishes from siblings like 'bitbucket_browse' (likely shows tree/UI) by emphasizing 'raw content'.

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?

The description implies usage with the 'at' parameter but does not explicitly say when to use this tool vs alternatives like code_search or browse. No when-not-to-use or exclusion guidance is provided.

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