Backlog MCP Server

List pull requests

list_pull_requests

Retrieve and view pull requests from a Backlog git repository to monitor code review status and manage development workflow.

Instructions

List pull requests in a Backlog git 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": {
      "projectIdOrKey": "<projectIdOrKey>",
      "repoIdOrName": "<repoIdOrName>"
    },
    "name": "list_pull_requests"
  }
}

Input Schema

Name	Required	Description	Default
`projectIdOrKey`	Yes
`repoIdOrName`	Yes
`statusId`	No
`assigneeId`	No
`createdUserId`	No
`offset`	No
`count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Apr 16, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't mention pagination (despite offset/count parameters), rate limits, authentication needs, or what the output looks like. This is a significant gap for a tool with 7 parameters and no output schema.

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 a single, clear sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a basic list operation, though this conciseness comes at the cost of completeness.

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 the complexity (7 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain parameter usage, output format, pagination, or how it differs from siblings. For a list tool with filtering capabilities, more context is needed to help the agent use it correctly.

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 description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'Backlog git repository' which hints at the context for projectIdOrKey and repoIdOrName, but doesn't explain any of the 7 parameters—especially filtering parameters like statusId, assigneeId, or pagination parameters offset/count. The description adds minimal value 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?

The description clearly states the action ('List') and resource ('pull requests in a Backlog git repository'), making the purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'get_pull_request' or 'list_issues', which would require more specificity about scope or filtering capabilities.

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 provides no guidance on when to use this tool versus alternatives like 'get_pull_request' (for single PR details) or 'list_issues' (for issues instead of PRs). There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Deploy Server