Skip to main content
Glama
Sign In
Bitbucket MCP

Bitbucket MCP

by SamtheIII
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_changed_files

Retrieve changed files in a Bitbucket pull request or commit, including per-file line additions and deletions for code review and impact analysis.

Instructions

Get the list of files changed in a pull request or commit, with per-file line add/remove counts.

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": {
      "ref": "<ref>",
      "repoSlug": "<repoSlug>"
    },
    "name": "get_changed_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesPR number (e.g. "42") or commit hash (e.g. "a1b2c3d4")
repoSlugYesRepository slug (e.g. my-repo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not state that the tool is read-only, safe, or any potential side effects. While the operation is clearly a read, the lack of explicit safety information leaves gaps for the agent.

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 a single sentence of 20 words, directly front-loading the action. Every word adds value; no fluff or repetition. Ideal conciseness.

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 list tool, the description provides enough context: input (PR/commit) and output (file list with add/remove counts). The absence of an output schema is partially compensated. However, missing details like pagination or error cases prevent a perfect score.

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 coverage is 100%, so baseline is 3. The description does not add additional meaning beyond the schema's parameter descriptions (ref and repoSlug are already well-documented). No extra value is provided.

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 the verb 'Get', the resource 'list of files changed', and the scope ('pull request or commit') with explicit output ('per-file line add/remove counts'). It distinguishes itself from sibling tools like get_diff (full diff) and get_file_content (file content), making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., get_diff). The description only states what it does, leaving the agent to infer the use case without explicit when/when-not instructions.

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

Deploy Server

Other Tools