GitHub PR Reviewer MCP

github_pr_review

Analyzes GitHub pull requests to generate a detailed code review report, covering PR details, diffs, and file changes.

Instructions

GitHub Pull Request linkini alıp detaylı bir code review raporu oluşturur. PR'ın detaylarını, değişiklikleri ve dosyaları analiz eder.

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": {
      "pr_url": "<pr_url>"
    },
    "name": "github_pr_review"
  }
}

Input Schema

Name	Required	Description	Default
`pr_url`	Yes	GitHub Pull Request URL'i (örn: https://github.com/owner/repo/pull/123)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description must shoulder the responsibility of behavioral disclosure. It mentions analyzing changes and files but does not disclose authentication requirements, rate limits, output format, or whether the operation is read-only. This leaves significant behavioral uncertainty.

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 two sentences, front-loaded with the primary purpose and scope. Every word contributes to understanding the tool, with no redundancy or filler.

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?

There is no output schema, so the description should explain what the 'detailed code review report' contains or its structure. It only vaguely references analysis without specifics, leaving the agent uncertain about return values. It also fails to reference sibling tools for context.

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 fully documents the single parameter 'pr_url' with an example. The description adds no additional semantic meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 clearly states the tool's purpose: takes a GitHub PR link and creates a detailed code review report by analyzing PR details, changes, and files. This distinguishes it from sibling tools like github_pr_diff and github_pr_files, which focus on specific aspects of a PR.

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 description implies usage for obtaining a comprehensive review report, but it does not explicitly mention when to use this tool versus alternatives like github_pr_diff or github_pr_files. There is no direct 'use this instead of' guidance or exclusions.

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

Deploy Server