Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get user

bb_get_user

Looks up a Bitbucket user by slug or searches by name/email fragment on Server/DC, returning account details for identification and authentication.

Instructions

Look up a Bitbucket user. Pass userSlug for a direct lookup, or filter to search by name/email prefix (Server/DC only; on Cloud a call without userSlug returns the authenticated account).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bb_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoSearch users by name or email fragment (Server/DC only).
userSlugNoDirect lookup by user slug (on Cloud: username, uuid or account_id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/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. It usefully discloses a non-obvious behavior — on Cloud, a call without userSlug silently returns the authenticated account rather than searching — which is real added value. It says nothing about permissions/auth requirements, what happens when a slug does not resolve, or what a filtered search returns (single vs multiple), leaving meaningful gaps for a lookup tool.

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?

A single dense sentence: purpose first, then the two calling modes, then the platform caveat. Nothing is redundant and no sentence fails to earn its place.

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 two-optional-parameter lookup with no annotations and no output schema, the description covers both invocation paths and the Cloud quirk. It does not describe what a successful response contains (fields returned, whether filter yields a list) and gives no zero-result guidance, which the absent output schema would otherwise have to supply.

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 both parameters are already documented, and the schema even supplies the Cloud slug formats. The description reinforces the mode split and platform restriction for 'filter', which is modest but genuine added meaning. Baseline 3 applies since the schema does most of the work.

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 opening sentence names a specific verb and resource ('Look up a Bitbucket user') and immediately splits the operation into a direct-lookup mode versus a filter-search mode. No sibling tool in the catalog deals with users, so there is nothing to disambiguate against, but the two internal modes are clearly separated.

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

Usage Guidelines4/5

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

It tells the agent which parameter selects which mode ('Pass userSlug for a direct lookup, or filter to search by name/email prefix') and adds a platform condition (Server/DC only). It does not say what to do when a lookup fails or when neither is a good fit, but the context needed to choose a calling shape is present.

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