Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get a Bitbucket repository

bb_get_repository

Fetch a single Bitbucket repository by project key and repository slug to obtain its details and HTTP clone URL in a compact card.

Instructions

Fetch a single repository by project key and slug. Returns a compact card including the HTTP clone URL.

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

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key (on Cloud: workspace slug).
repositorySlugYesRepository slug, e.g. 'service-api'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return shape (a compact card containing the HTTP clone URL), which is genuinely useful with no output schema, but it says nothing about permission requirements, authentication scope, or whether a missing repository raises an error rather than returning empty.

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?

Two short sentences with zero waste: the operation and its keys come first, then the return value. Nothing is repeated and nothing padding-worthy was included.

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?

This is a low-complexity two-parameter read tool with fully documented parameters and no output schema, and the description supplies the one missing piece an agent would want — what comes back. Naming the auth/error behavior would make it complete, but the residual gap is small at this complexity.

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%, including the Cloud-vs-Server workspace-slug nuance for projectKey, so the schema already does the explanatory work. The description only restates that both parameters are required lookup keys and adds no format or edge-case detail beyond the schema.

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?

"Fetch a single repository by project key and slug" names a specific verb (fetch), a specific resource (single repository), and the lookup keys. The word "single" implicitly separates it from the plural bb_get_repositories, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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 only implied: an agent can infer this is the tool for one known repository versus listing many, but the description never states when to prefer it over bb_get_repositories or bb_browse_repository, nor does it mention prerequisites such as needing both key and slug. Minimum viable context with a clear gap around alternatives.

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