Bitbucket MCP Server

get_file_content

Retrieve the full raw text of any file in a Bitbucket repository by providing its repository slug and file path, returning source code for direct reading.

Instructions

Read the full content of a file in a repository. Returns the raw file content as text. Use this to read source code files.

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

Input Schema

Name	Required	Description
`path`	Yes	The file path (e.g., 'src/index.ts').
`branch`	No	The branch name. Defaults to the main branch.
`repo_slug`	Yes	The repository slug.
`workspace`	No	The workspace slug. Optional if BITBUCKET_WORKSPACE env var is set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool returns raw file content as text, which is helpful, but it does not mention potential limitations like file size, binary files, or authentication requirements. The description adds some transparency but is not thorough.

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 three short, direct sentences with no redundant wording. The core action, return format, and use case are each given their own sentence, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple file-reading tool, the description covers the essential action and return format, and the schema documents parameters. However, the absence of annotations and the lack of guidance on when to prefer this over sibling tools (e.g., get_readme for README files) leaves some contextual gaps.

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 four parameters are already documented in the schema. The description repeats that the tool reads files but adds no additional meaning about parameters such as branch defaults or workspace resolution. Baseline 3 is appropriate.

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 clearly states the verb 'Read' and the resource 'a file in a repository', and specifies the return type as raw text. It implies use for source code but does not explicitly distinguish itself from sibling tools like get_readme or browse_directory, so it falls short of a full 5.

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 phrase 'Use this to read source code files' provides an implied usage context, but there is no explicit guidance on when to choose this tool over alternatives such as get_readme or search_code. No exclusions or when-not-to-use conditions are given.

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

Deploy Server