Skip to main content
Glama

bitbucket_list_pull_requests

Read-onlyIdempotent

Retrieve pull requests from a Bitbucket repository, with optional filters for state and result limit, to review open, merged, declined, or superseded PRs.

Instructions

List pull requests for a Bitbucket repository.

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": {
      "username": "<username>",
      "app_password": "<app_password>",
      "workspace": "<workspace>",
      "repo": "<repo>"
    },
    "name": "bitbucket_list_pull_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository slug
limitNoPRs to return (max 50, default 25)
stateNoFilter by PR state
usernameYesBitbucket username
workspaceYesWorkspace id
app_passwordYesBitbucket app password

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination, default result count, whether state defaults to OPEN, or that app_password credentials are needed per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification for a tool that requires four credentials/config inputs.

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

Completeness2/5

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

There is no output schema, and the description says nothing about return shape, ordering, or pagination behavior when the repository has more PRs than the limit. For an authenticated list operation with six parameters, this leaves meaningful gaps.

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 each of the six parameters documented including the state enum and the limit cap of 50/default 25. The description contributes no additional parameter meaning, 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?

States a specific verb (list) and resource (pull requests) scoped to a Bitbucket repository, so the agent knows exactly what the tool returns. It does not differentiate itself from related siblings like bitbucket_list_repos or bitbucket_get_repo, but the resource noun is distinctive enough.

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

Usage Guidelines2/5

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

The description gives no when-to-use context, no alternatives, and no exclusions. An agent must infer from the name alone that this is the read path versus repository-level tools.

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