bitbucket-mcp-server

list-issues

Retrieve repository issues from Bitbucket with filters for kind, state, and pagination to review bugs, tasks, enhancements, and proposals.

Instructions

List issues for a 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": {
      "repo_slug": "<repo_slug>"
    },
    "name": "list-issues"
  }
}

Input Schema

Name	Required	Description
`kind`	No	Filter by issue kind
`page`	No	Page number or opaque next page URL returned by Bitbucket pagination
`state`	No	Filter by issue state
`pagelen`	No	Number of items per page (default: 10, min: 10, max: 100)
`repo_slug`	Yes	Repository slug/name
`workspace`	No	Bitbucket workspace name. Falls back to BITBUCKET_WORKSPACE env var if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Nov 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and adds essentially nothing beyond the name: it does not state that results are paginated, that filters are combinable, default page size, permission requirements, or ordering. For a list operation with zero annotation coverage this leaves meaningful behavioral questions unanswered.

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

Conciseness3/5

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

A single short sentence with zero padding, but also no structure or front-loaded detail beyond the bare minimum. It is concise to the point of under-specification rather than efficient communication.

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

Completeness3/5

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

For a simple read-only list tool whose six parameters are fully self-documented in the schema and which has no output schema, the core information is available elsewhere. Still, the description should at minimum note pagination behavior and auth/workspace expectations, which it omits.

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%: every parameter (repo_slug, workspace, state, kind, page, pagelen) is documented with types, enums, defaults and env fallback. The description adds no parameter meaning of its own, so the baseline 3 applies – the schema does all the work.

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 and resource: 'List issues for a repository'. An agent immediately knows this is a read operation returning issues scoped to one repo; the only gap is that it does not distinguish itself from any sibling, though no sibling in the provided list appears to list issues.

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?

There is no when-to-use guidance, no prerequisites (e.g., auth or workspace requirements), and no mention of alternatives or when-not to use it. The agent must infer usage entirely from the name.

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

Deploy Server