CNB Remote MCP

Overview Schema Source Related Servers Discussions Admin

List PR reviews

pr_review_list

Read-onlyIdempotent

Lists a pull request's reviews, including approvals, change requests, and comments, so you can inspect review status and feedback by repository and PR number.

Instructions

List reviews of a pull request (approve / request changes / comment).

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": "<repo>",
      "number": "<number>"
    },
    "name": "pr_review_list"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes	Repository path, e.g. "owner/repo" or "group/subgroup/repo"
`number`	Yes	PR number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description's only added behavioral value is signaling that results are review-type records with states (approve / request changes / comment); it says nothing about ordering, pagination, or whether stale/dismissed reviews are included.

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?

A single front-loaded sentence with the resource first and the clarifying parenthetical second; no filler and nothing to trim.

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

Completeness4/5

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

For a simple two-parameter read tool whose annotations carry the safety profile and whose schema documents both inputs, the description covers what is needed to invoke it. The only gap is that no output schema exists and the description does not sketch the shape or volume of returned reviews.

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 both repo path format and PR number already documented in the schema. The description adds no meaning beyond that, which is acceptable given the schema does the work, but nothing extra is contributed.

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?

Names a specific verb and resource ("List reviews of a pull request") and clarifies the resource by enumerating the review states returned (approve / request changes / comment), which separates it in spirit from pr_comment_list. It stops short of explicitly contrasting with siblings such as pr_get or pr_comment_list.

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?

Usage is implied by the object it operates on — an agent knows to call it when it needs review verdicts for a given PR. There is no explicit when-to-use versus pr_comment_list or pr_get, and no mention of prerequisites such as the PR needing to exist.

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