Skip to main content
Glama
Sign In
bitbucket-mcp-server

bitbucket-mcp-server

by WilliamLINWEN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pull-requests

List pull requests for a Bitbucket repository or get details for one by providing its ID. Filter by state and paginate results.

Instructions

List pull requests for a repository, or get details for a single pull request when pr_id is provided.

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": {
      "repo_slug": "<repo_slug>"
    },
    "name": "pull-requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo(list only) Page number or opaque next page URL
pr_idNoPull request ID. If provided, returns a single PR; otherwise lists.
stateNo(list only) Filter by state. Accepts a single state or an array of states: OPEN, MERGED, DECLINED, SUPERSEDED
pagelenNo(list only) Items per page (10-100, default 10)
repo_slugYesRepository slug/name
workspaceNoBitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.3/5.0
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. Beyond implying read-only listing/detail retrieval, it does not disclose authentication requirements, pagination behavior, default filtering, or what the returned data includes.

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 definition is a single front-loaded sentence with no wasted wording. The conditional mode switch is expressed compactly and clearly.

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

Completeness3/5

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

For a dual-mode list/detail tool with six parameters but no output schema, the description covers the core selection logic adequately. It still omits useful context such as default listing state, pagination expectations, and the shape of returned PR details.

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 the schema already documents all six parameters thoroughly. The description only restates the `pr_id` mode switch and adds no additional parameter semantics beyond the input schema.

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 states a specific verb and resource: list pull requests or get details for a single pull request. It clearly distinguishes the two operating modes via `pr_id`, though it does not differentiate against siblings such as `get-pr-diff` or `pr-comments`.

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?

It gives a clear mode-selection rule: provide `pr_id` for a single PR, otherwise list PRs. However, it does not explain when to use this tool instead of related siblings or mention any exclusions or prerequisites.

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