Skip to main content
Glama
MCP Dokploy Online
by igoruam

bitbucket-getBitbucketRepositories

Read-onlyIdempotent

Retrieves the repositories linked to a specified Bitbucket ID, enabling you to list available repositories for deployment or infrastructure workflows.

Instructions

GET /bitbucket.getBitbucketRepositories

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": {
      "bitbucketId": "<bitbucketId>"
    },
    "name": "bitbucket-getBitbucketRepositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitbucketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is known; the description adds nothing beyond confirming it is a GET-style read. No mention of pagination, result ordering, or what happens when the bitbucketId is invalid or the provider is unreachable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short, but only because it is under-specified rather than economical; a raw route path is not front-loaded, purposeful prose. Nothing in the sentence helps an agent decide or invoke correctly.

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?

With no output schema and an undocumented required parameter, the description carries the full burden of explaining what the call needs and returns, and it does neither. For a provider-scoped listing tool, the omission of the ID's meaning and the return shape leaves genuine gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, bitbucketId, with 0% schema description coverage, and the description says nothing about it. It does not clarify whether it is a provider connection ID, a workspace slug, or a numeric index, which is the main ambiguity an agent would hit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the raw endpoint string "GET /bitbucket.getBitbucketRepositories", which merely restates the tool name rather than explaining what it does. An agent can infer it lists repositories tied to a bitbucket, but gets no statement of scope, filtering, or how it differs from siblings like getBitbucketBranches.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to, or which sibling to prefer (e.g., gitea/github/gitlab repository listers). The agent must infer everything from the name.

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