bbkt

by zach-snell

Overview Schema Source Related Servers Discussions Admin

Hybrid

manage_source

Read, write, delete files; list directories; view history; and search code in Bitbucket repositories.

Instructions

Unified tool for source code operations (read, list_directory, get_history, search, write, delete)

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": {
      "action": "<action>",
      "workspace": "<workspace>",
      "repo_slug": "<repo_slug>"
    },
    "name": "manage_source"
  }
}

Input Schema

Name	Required	Description
`ref`	No	Commit hash, branch, or tag (default: HEAD)
`page`	No	Page number
`path`	No	Path to the file or directory
`query`	No	Search query
`action`	Yes	Action to perform: 'read_file', 'list_directory', 'get_history', 'search', 'write_file', 'delete_file'
`author`	No	Commit author in 'Name <email>' format
`branch`	No	Branch to commit to
`content`	No	Content to write to the file
`message`	No	Commit message
`pagelen`	No	Results per page
`max_depth`	No	Maximum depth of recursion (for list_directory)
`repo_slug`	Yes	Repository slug
`workspace`	Yes	Workspace slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Mar 16, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the operations available but doesn't describe their behavior: what 'read' returns, what 'write' commits to, whether 'delete' is permanent, authentication requirements, rate limits, or error conditions. The description is essentially a feature list without behavioral context.

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?

The description is extremely concise - a single sentence listing the available actions. While efficient, it may be too terse given the tool's complexity. The structure is front-loaded with the unified nature of the tool, but could benefit from more context about what 'source code operations' means.

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

Completeness2/5

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

For a complex tool with 13 parameters, 6 different actions, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool actually does with source code, how actions differ, what resources they operate on, or what to expect as results. The description fails to compensate for the lack of structured metadata.

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 the schema already documents all 13 parameters thoroughly. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain how parameters interact with different actions, which parameters are required for which actions, or provide examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 this is a 'unified tool for source code operations' and lists the specific actions available (read, list_directory, get_history, search, write, delete). It distinguishes itself from siblings by focusing on source code operations rather than commits, issues, pipelines, etc. However, it doesn't specify what resource it operates on (files/directories in repositories).

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?

The description provides no guidance on when to use this tool versus the sibling tools. While it lists the available actions, it doesn't indicate when to choose this unified tool over more specialized ones like manage_commits or manage_repositories. There's no mention of prerequisites, constraints, or typical use cases.

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

Deploy Server