GitHub MCP Server

create_pr

Create a pull request on GitHub by providing repository owner, name, title, and head branch, with optional base and description.

Instructions

Create a pull request

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "title": "<title>",
      "head": "<head>"
    },
    "name": "create_pr"
  }
}

Input Schema

Name	Required	Description	Default
`base`	No	Branch to merge into	main
`body`	No	Pull request description
`head`	Yes	Branch containing changes
`repo`	Yes	Repository name
`owner`	Yes	Repository owner (username or org)
`title`	Yes	Pull request title

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It only mentions 'create', implying a write operation, but discloses no side effects, prerequisites, or return behavior. This is minimal and mirrors the mid-tier example that scored 2.

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, front-loaded sentence with zero filler words. It is highly concise and clearly structured, making it easy to parse quickly.

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?

Despite a complete schema, the description lacks essential context such as what a pull request is, what inputs are needed, or expected outcomes. With no annotations and no output schema, this minimal description is insufficient for a tool with six parameters.

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 has 100% description coverage for all six parameters, so the schema already provides parameter semantics. The description adds no extra meaning beyond the schema, matching the baseline of 3 for high coverage.

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 'Create a pull request' uses a specific verb and resource, clearly stating the tool's action and target. It distinguishes itself from sibling tools like get_pr, merge_pr, list_prs, and comment_on_pr by implying a creation operation.

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 guidance on when to use this tool vs. alternatives. The description simply states the action without context, exclusions, or comparison to sibling tools, so the agent gets no explicit usage direction.

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

Deploy Server