Skip to main content
Glama
Sign In
Bitbucket MCP Server

Bitbucket MCP Server

by pdogra1299
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_pull_requests

Read-only

List pull requests in a Bitbucket repository, or omit the repository to view your PRs across all repos with role, state, author, and pagination filters.

Instructions

List pull requests in a repository. Omit repository (Server only) to list YOUR PRs across all repos in one call (filter with role).

Input Schema

NameRequiredDescriptionDefault
roleNoCross-repo mode only
limitNoMax results (default 25)
startNoPagination start (default 0)
stateNoDefault OPEN
authorNoFilter by author username
workspaceYesProject key (e.g., PROJ)
repositoryNoRepository slug; omit for cross-repo dashboard (Server)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv3.0.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of PRs to return (default: 25)"New value: +"Max results (default 25)"
    • changedInput schema / properties / repository / description
      Previous value: -"Repository slug (e.g., \"my-repo\")"New value: +"Repository slug; omit for cross-repo dashboard (Server)"
    • addedInput schema / properties / role
      Added value: +{
+  "description": "Cross-repo mode only",
+  "enum": [
+    "AUTHOR",
+    "REVIEWER",
+    "PARTICIPANT"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / start / description
      Previous value: -"Start index for pagination (default: 0)"New value: +"Pagination start (default 0)"
    • changedInput schema / properties / state / description
      Previous value: -"Filter by PR state: OPEN, MERGED, DECLINED, ALL (default: OPEN)"New value: +"Default OPEN"
    • changedInput schema / properties / workspace / description
      Previous value: -"Bitbucket workspace/project key (e.g., \"PROJ\")"New value: +"Project key (e.g., PROJ)"
    • changedInput schema / required
      Previous value: -[
-  "workspace",
-  "repository"
-]New value: +[
+  "workspace"
+]
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes safety, so the description appropriately focuses on the non-obvious cross-repo behavior. It discloses the Server-only constraint for omitting `repository` and the fact that this returns your PRs across all repos in one call.

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 two tight sentences with no wasted text. The repository-scoped case is stated first, and the cross-repo exception follows immediately.

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?

Given the rich schema and readOnly annotation, the description covers the main operational distinction an agent needs: repository-scoped listing versus cross-repo listing. It does not describe the return shape, but for a simple list tool with no output schema that is a minor gap.

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 seven parameters including role, state, limit, start, author, workspace, and repository. The description adds some meaning about repository omission and role filtering, but mostly reinforces what the schema already says.

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

Purpose5/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: listing pull requests in a repository. It also distinguishes the cross-repo mode from the normal repository-scoped mode, which differentiates it from siblings such as get_pull_request.

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

Usage Guidelines4/5

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

It clearly explains the key usage branch: omit `repository` to list your PRs across all repos, and use `role` to filter that cross-repo view. It does not explicitly name sibling alternatives like get_pull_request, but the main mode selection is clear.

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