Skip to main content
Glama
jlromano

Bitbucket MCP Server

by jlromano

get_repository

Retrieve detailed information about a specific Bitbucket repository by providing its workspace and repository slug identifiers.

Instructions

Get details of a specific repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceYesThe workspace slug
repo_slugYesThe repository slug

Implementation Reference

  • The handler method that calls the Bitbucket API to fetch repository details.
    async getRepository(workspace: string, repoSlug: string): Promise<Repository> {
      const response = await this.api.get(`/repositories/${workspace}/${repoSlug}`);
      return response.data;
    }
  • Tool definition and input schema registration for get_repository.
    {
      name: 'get_repository',
      description: 'Get details of a specific repository',
      inputSchema: {
        type: 'object',
        properties: {
          workspace: {
            type: 'string',
            description: 'The workspace slug',
          },
          repo_slug: {
            type: 'string',
            description: 'The repository slug',
          },
        },
        required: ['workspace', 'repo_slug'],
      },
    },
  • src/index.ts:425-436 (registration)
    Registration of the tool logic within the main server request handler loop.
    case 'get_repository': {
      const { workspace, repo_slug } = args as { workspace: string; repo_slug: string };
      const repository = await client.getRepository(workspace, repo_slug);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(repository, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'Get details' but doesn't clarify if this is a read-only operation, what permissions are required, how errors are handled, or the format of returned details. This leaves significant gaps for a tool with no annotation support.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand quickly.

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?

Given the complexity of a repository details tool with no annotations and no output schema, the description is incomplete. It lacks information on what details are returned, error conditions, or behavioral traits, making it insufficient for an agent to fully understand how to use this tool effectively.

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?

The schema description coverage is 100%, so the input schema already documents both parameters ('workspace' and 'repo_slug') adequately. The description adds no additional meaning beyond what the schema provides, such as examples or context for the parameters, meeting the baseline for high schema coverage.

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 clearly states the verb ('Get') and resource ('details of a specific repository'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'list_repositories' or 'get_branch', which would require more specificity about what 'details' includes to reach a score of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a specific repository, or compare it to siblings like 'list_repositories' for broader queries or 'get_branch' for branch-specific details, leaving usage context unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jlromano/bitbucket-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server