list-pull-requests

List and filter Bitbucket pull requests by repository, status, or author to track code review progress or retrieve PR IDs for Bitbucket operations. Includes pagination support for large result sets.

Instructions

List Bitbucket pull requests with optional filtering capabilities.

PURPOSE: Allows you to find and browse pull requests across repositories with filtering options.

WHEN TO USE:

When you need to find pull requests within a specific repository
When you want to check PR status (open, merged, declined, etc.)
When you need to track code review activity and progress
When you need PR IDs for other Bitbucket operations
When monitoring contributions from specific authors

WHEN NOT TO USE:

When you don't know which repository to look in (use list-repositories first)
When you already know the PR ID (use get-pull-request instead)
When you need detailed PR content or comments (use get-pull-request instead)
When you need to browse repositories rather than PRs (use list-repositories)

RETURNS: Formatted list of pull requests with IDs, titles, states, authors, branch information, and URLs, plus pagination info.

EXAMPLES:

List all PRs in a repo: {workspace: "myteam", repoSlug: "project-api"}
Filter by state: {workspace: "myteam", repoSlug: "project-api", state: "OPEN"}
With pagination: {workspace: "myteam", repoSlug: "project-api", limit: 10, cursor: "next-page-token"}

ERRORS:

Repository not found: Verify workspace and repository slugs
Authentication failures: Check your Bitbucket credentials
Permission errors: Ensure you have access to the requested repository
Rate limiting: Use pagination and reduce query frequency

Input Schema

Name	Required	Description
`cursor`	No	Pagination cursor for retrieving the next set of results. Obtain this value from the previous response when more results are available.
`limit`	No	Maximum number of pull requests to return (1-100). Use this to control the response size. If omitted, defaults to 25.
`repoSlug`	Yes	Repository slug containing the pull requests. This must be a valid repository in the specified workspace. Example: "project-api"
`state`	No	Filter pull requests by state. Options: "OPEN" (active PRs), "MERGED" (completed PRs), "DECLINED" (rejected PRs), or "SUPERSEDED" (replaced PRs). If omitted, defaults to showing all states.
`workspace`	Yes	Workspace slug containing the repository. Must be a valid workspace slug from your Bitbucket account. Example: "myteam"

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "cursor": {
      "description": "Pagination cursor for retrieving the next set of results. Obtain this value from the previous response when more results are available.",
      "type": "string"
    },
    "limit": {
      "description": "Maximum number of pull requests to return (1-100). Use this to control the response size. If omitted, defaults to 25.",
      "exclusiveMinimum": 0,
      "maximum": 100,
      "type": "integer"
    },
    "repoSlug": {
      "description": "Repository slug containing the pull requests. This must be a valid repository in the specified workspace. Example: \"project-api\"",
      "minLength": 1,
      "type": "string"
    },
    "state": {
      "description": "Filter pull requests by state. Options: \"OPEN\" (active PRs), \"MERGED\" (completed PRs), \"DECLINED\" (rejected PRs), or \"SUPERSEDED\" (replaced PRs). If omitted, defaults to showing all states.",
      "enum": [
        "OPEN",
        "MERGED",
        "DECLINED",
        "SUPERSEDED"
      ],
      "type": "string"
    },
    "workspace": {
      "description": "Workspace slug containing the repository. Must be a valid workspace slug from your Bitbucket account. Example: \"myteam\"",
      "minLength": 1,
      "type": "string"
    }
  },
  "required": [
    "workspace",
    "repoSlug"
  ],
  "type": "object"
}

Atlassian Bitbucket MCP Server