Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get dashboard pull requests

bb_get_dashboard_pull_requests

Lists the authenticated user's dashboard pull requests, filtered by role (author, reviewer, participant) and state (open, merged, declined, all) to focus on relevant reviews or code changes.

Instructions

List the pull requests of the authenticated user from the dashboard, filterable by role (AUTHOR|REVIEWER|PARTICIPANT) and state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bb_get_dashboard_pull_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number (Cloud only).
roleNoYour role in the pull requests.REVIEWER
limitNoPage size (1-1000).
startNoZero-based page offset (Server/DC).
stateNoPull request state filter.OPEN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; 'List' clearly signals a non-mutating read, and it discloses that results are scoped to the authenticated user. It says nothing about result ordering, pagination behaviour, or the fact that paging is platform-dependent (page for Cloud, start for Server/DC), which are the traits an agent would most want here.

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 with the resource, the scope qualifier, and the filterable dimensions in that order, with no filler or redundant restatement of the name.

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 five-parameter read-only listing with full schema coverage and no output schema, the definition covers the essentials; only the absence of any note on pagination/platform differences and expected ordering keeps it from being fully complete.

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%, with both enums and the Cloud vs Server/DC pagination split already documented in the schema. The description only restates role and state filtering and adds no syntax or defaulting nuance beyond it, so baseline 3 applies.

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 gives a specific verb (List) and resource (pull requests) and narrows the scope to the authenticated user's dashboard, which separates it from a generic repo-wide listing. It stops short of naming the sibling it differs from, so the agent must infer that distinction from the scope phrase alone.

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?

The phrase 'from the dashboard' and the role/state filters imply the intended context, but there is no explicit statement of when to prefer this over bb_list_pull_requests or bb_get_inbox_pull_requests, and no exclusions or prerequisites are given.

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