Skip to main content
Glama

bitbucket_get_repo

Read-onlyIdempotent

Fetch a single Bitbucket repository by workspace and repo slug using username and app password authentication.

Instructions

Get a single Bitbucket repository.

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": {
      "username": "<username>",
      "app_password": "<app_password>",
      "workspace": "<workspace>",
      "repo": "<repo>"
    },
    "name": "bitbucket_get_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository slug
usernameYesBitbucket username
workspaceYesWorkspace id
app_passwordYesBitbucket app password

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, dangerous=false and openWorld=true, so the safety profile is covered. The description adds nothing beyond that: no note that responses are scoped to the supplied workspace, that app_password is a credential, or what happens on a nonexistent repo. For a 4-required-param authenticated call, the description contributes no 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?

One short, front-loaded sentence with no filler. It is efficient but borders on under-specified rather than tight — nothing extra was packed in to earn the space it uses.

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?

There is no output schema and no annotations covering authentication, yet the description says nothing about the returned object, the credential requirement, or failure modes. For a tool requiring four mandatory parameters including an app password, the definition is too thin to fully prepare an agent.

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%, with each of repo, username, workspace and app_password documented in the schema, so the baseline applies. The description supplies no additional semantics — e.g. that repo is a slug rather than a UUID, or that workspace must match the token's access — leaving the schema to do all 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?

States a concrete verb and resource ("Get a single Bitbucket repository"), and the word "single" implicitly separates it from the list operation. It never names a sibling or scoping rule explicitly, so the differentiation is inferential 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 by "single" — an agent can guess this is the fetch-one path versus bitbucket_list_repos, but the description offers no explicit when-to-use, no preconditions, and no note on how the repo is identified (workspace + slug).

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