Bitbucket Server MCP

unwatch_pull_request

Unsubscribe from watching a pull request to stop receiving notifications. Use this to manage your watch list and reduce notification clutter.

Instructions

Unsubscribe from watching a pull request.

Args: project_key: The project key. repo_slug: The repository slug. pr_id: The pull request ID.

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

Input Schema

Name	Required	Description	Default
`project_key`	Yes
`repo_slug`	Yes
`pr_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0May 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'unsubscribe from watching' without clarifying whether it removes only the current user, if it's idempotent, or what happens if not currently watching. Critical behavioral traits like permissions or reversibility are missing.

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?

The description is concise and front-loaded with the action. It uses a single informative sentence plus parameter listing. However, the parameter descriptions are redundant with the schema, which slightly reduces efficiency.

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?

Given no annotations and a simple input schema, the description should provide more context about what 'unwatching' entails, such as whether it requires prior subscription, effects on notifications, or relation to the 'watch_pull_request' counterpart. The presence of an output schema is unknown, but the description itself is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description should add meaning beyond the schema. However, it merely lists parameter names (project_key, repo_slug, pr_id) without providing format, examples, or context. The schema already defines them, so no value is added.

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 clearly states the action 'unsubscribe from watching a pull request.' It uses a specific verb+resource combination that distinguishes it from the sibling tool 'watch_pull_request.' However, it does not elaborate on the scope (e.g., for the current user or all watchers).

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?

No guidance is provided on when to use this tool versus alternatives like 'watch_pull_request' or other PR tools. The description only implies the action but lacks context on prerequisites, side effects, or whether the user must be currently watching.

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

Deploy Server