Skip to main content
Glama
jlromano

Bitbucket MCP Server

by jlromano

get_pull_request

Retrieve detailed information about a specific Bitbucket pull request using workspace, repository, and PR ID parameters.

Instructions

Get details of a specific pull request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceYesThe workspace slug
repo_slugYesThe repository slug
pr_idYesThe pull request ID

Implementation Reference

  • The actual implementation of getPullRequest that interacts with the Bitbucket API.
    async getPullRequest(workspace: string, repoSlug: string, prId: number): Promise<PullRequest> {
      const response = await this.api.get(`/repositories/${workspace}/${repoSlug}/pullrequests/${prId}`);
      return response.data;
    }
  • The MCP tool handler in index.ts that calls BitbucketClient.getPullRequest.
    case 'get_pull_request': {
      const { workspace, repo_slug, pr_id } = args as {
        workspace: string;
        repo_slug: string;
        pr_id: number;
      };
      const pullRequest = await client.getPullRequest(workspace, repo_slug, pr_id);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(pullRequest, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details but doesn't describe what 'details' include, whether it's a read-only operation, error conditions (e.g., invalid IDs), authentication needs, or rate limits. This leaves significant gaps for a tool that likely interacts with a version control system.

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?

The description is a single, direct sentence that efficiently conveys the core action. It's front-loaded with the main purpose and avoids unnecessary words, though it could be slightly more informative without losing conciseness.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what details are returned (e.g., title, status, diff), error handling, or system-specific behaviors. For a tool with three parameters and likely complex data retrieval, this minimal description leaves too much undefined for effective agent use.

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 input schema has 100% description coverage, clearly documenting all three required parameters (workspace, repo_slug, pr_id). The description adds no parameter-specific information beyond implying a pull request ID is needed, so it meets the baseline of 3 where the schema does the heavy lifting.

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 tool's purpose as retrieving details of a specific pull request, using the verb 'Get' and specifying the resource 'pull request'. It distinguishes from siblings like list_pull_requests (which lists multiple) but doesn't explicitly differentiate from get_repository or get_commit, which retrieve different resource types.

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 (e.g., needing a specific pull request ID), contrast with list_pull_requests for browsing, or indicate when other tools like get_commit might be more appropriate for related data.

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