Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get pull request

bb_get_pull_request

Fetch a single pull request as a compact card with truncated description, branch pair, and reviewer decisions. Use it to inspect PR details before review or merge.

Instructions

Fetch one pull request with description (truncated), branch pair, reviewers and their decisions as a compact card.

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": {
      "projectKey": "<projectKey>",
      "repositorySlug": "<repositorySlug>",
      "pullRequestId": "<pullRequestId>"
    },
    "name": "bb_get_pull_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key (on Cloud: workspace slug).
pullRequestIdYesPull request id, e.g. 101.
repositorySlugYesRepository slug, e.g. 'service-api'.
maxDescriptionCharsNoMaximum description characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/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, but it does useful work by disclosing the return shape: a compact card with truncated description, branch pair, and reviewer decisions. It says nothing about authentication requirements, error behavior when the PR id is invalid, or pagination/limits, so the coverage is partial rather than complete.

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 front-loaded sentence naming the action, the scope, and the returned fields, with no filler. Every clause contributes information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read tool with no output schema, the description correctly spends its budget describing what comes back rather than repeating inputs, and the truncation note sets expectations about payload size. It is nearly complete, missing only selection guidance relative to sibling PR readers.

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 all four parameters (projectKey, repositorySlug, pullRequestId, maxDescriptionChars) are already documented with examples and bounds. The description's mention of a truncated description is a light hint toward maxDescriptionChars but adds no format or default details beyond the schema, which fits the baseline.

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?

"Fetch one pull request" gives a specific verb and singular resource, and the payload summary (description, branch pair, reviewers with decisions) tells an agent what it gets back. It stops short of naming how it differs from adjacent readers like bb_get_pull_request_changes or bb_get_pull_request_diff, so an agent must infer that those cover files rather than the PR card itself.

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 word "one" implies single-record retrieval versus a list, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. An agent gets no guidance on choosing this over bb_list_pull_requests, bb_get_pr_comments_and_actions, or the diff/changes siblings.

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