Bitbucket MCP

decline_pull_request

Reject an open pull request by providing the repository slug and pull request ID, with an optional message. Block unwanted merges before they are completed.

Instructions

Decline (reject) an open pull request

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": {
      "repo_slug": "<repo_slug>",
      "pr_id": "<pr_id>"
    },
    "name": "decline_pull_request"
  }
}

Input Schema

Name	Required	Description
`pr_id`	Yes	Pull request ID
`message`	No	Optional message
`repo_slug`	Yes	Repository slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-developmentSep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only names the action without explaining what declining does to the pull request, whether it is reversible, or what side effects occur.

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 one short, front-loaded sentence with no filler words. The parenthetical 'reject' reinforces intent without adding unnecessary length.

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?

For a mutation tool with no annotations and no output schema, the description is too thin. It does not disclose consequences, prerequisites beyond 'open', permissions, reversibility, or what the caller should expect after invocation.

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?

The input schema covers 100% of parameters, so the schema already documents repo_slug, pr_id, and message. The description adds no parameter-level meaning beyond the core intent, which is acceptable given full schema coverage.

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 ('Decline (reject)') and a specific resource ('an open pull request'), making the operation immediately recognizable. It also distinguishes this tool from siblings like merge_pull_request, approve_pull_request, and request_pr_changes by naming a distinct action.

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 'an open pull request' implies the valid target state and gives some contextual guidance. However, it does not explicitly say when to prefer this over request_pr_changes or merge_pull_request, nor does it mention any exclusions.

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