Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get a Bitbucket project

bb_get_project

Fetch a single Bitbucket project by key and return a compact card with its key, name, description, and visibility for quick project lookup.

Instructions

Fetch a single project by key and return it as a compact card (key, name, description, visibility).

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

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key (on Cloud: workspace slug).

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 behavioral burden. It correctly conveys a non-mutating read and discloses the return payload (key, name, description, visibility), but says nothing about permission/auth requirements or what happens when the key does not exist.

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?

One sentence, front-loaded with the action and resource, with the return shape appended parenthetically. There is no boilerplate or redundant wording to trim.

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 one-parameter read tool with no output schema, the description covers the operation and enumerates the returned fields, which is enough to call it correctly. Only error/not-found behavior is unaddressed, a minor gap 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 coverage is 100% and the single projectKey parameter is already documented in the schema including the Cloud workspace-slug note. The description only restates "by key" and adds no format or edge-case detail beyond the structured field, so the baseline 3 applies.

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 pairs a specific verb ("Fetch") with a specific resource ("a single project by key") and states the returned shape, so an agent can distinguish it from a list-style sibling like bb_get_projects by the word "single". It stops short of naming the list alternative explicitly, which keeps it out of 5 territory.

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: "a single project by key" signals this is the one-project lookup versus a listing call, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. An agent can infer the right context but must do the inference itself.

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