Skip to main content
Glama
bitbucket-mcp

bitbucket-mcp

by nevzatcirak

Get inbox pull requests

bb_get_inbox_pull_requests

Lists pull requests in the authenticated user's Bitbucket inbox that need attention, ordered by newest activity first.

Instructions

List the pull requests in the authenticated user's inbox (things that need attention), newest activity first.

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_inbox_pull_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-1000).
startNoZero-based page offset.

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?

With no annotations supplied, the description carries the full burden. It usefully discloses result ordering (newest activity first) and that results are scoped to the authenticated user, but says nothing about permission requirements, what the inbox criteria actually are (review requested? assigned? mentioned?), or pagination behavior beyond the schema fields.

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 that states resource, scope, and ordering with no filler. Nothing could be removed without losing information.

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 simple two-parameter read-only list tool with a fully documented schema and no output schema, the description covers purpose, scope, and ordering adequately. It could be stronger by clarifying what qualifies as "inbox" and how it differs from the other PR-listing tools, but nothing essential to invoking it is missing.

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 limit and start both documented in the schema, so the baseline is 3. The description adds no extra meaning about page size, offset semantics, or maximum paging depth, so it neither helps nor harms beyond the 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?

"List the pull requests in the authenticated user's inbox" gives a specific verb and resource with a clearly bounded scope, and the parenthetical "(things that need attention)" defines what "inbox" means. It does not name or explicitly distinguish itself from siblings like bb_list_pull_requests or bb_get_dashboard_pull_requests, so it stops short of a 5.

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 "things that need attention" implies when this tool is appropriate (an attention-focused view rather than a general listing), but there is no explicit when-not-to-use guidance or named alternative. An agent must infer the contrast with bb_list_pull_requests and bb_get_dashboard_pull_requests on its own.

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