mcp-saas-toolkit

github_create_pull_request

Create a GitHub pull request by specifying source and target branches, title, body, and optional draft status. Merge changes between branches.

Instructions

Create a pull request in a GitHub repository. Specify source and target branches, title, and body.

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>",
      "base": "<base>"
    },
    "name": "github_create_pull_request"
  }
}

Input Schema

Name	Required	Description
`base`	Yes	The branch to merge into (target), e.g. 'main'
`body`	No	PR description (supports Markdown)
`head`	Yes	The branch containing changes (source). Use 'user:branch' for cross-fork PRs.
`repo`	Yes	Repository name
`draft`	No	Create as a draft PR. Default: false
`owner`	Yes	Repository owner
`title`	Yes	Pull request title

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. However, it only states the basic action and required inputs. It does not disclose behavioral traits such as authentication needs, error handling (e.g., if branches don't exist), rate limits, or what happens upon creation (e.g., triggering CI checks). This is insufficient for a mutation tool.

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

Conciseness4/5

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

The description is a single concise sentence that front-loads the purpose. It efficiently communicates the core action and key inputs. Although it could benefit from additional context, it is not overly verbose.

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?

Given the high schema coverage and lack of output schema, the description provides the minimum context to understand the tool's input. However, it does not explain the return value (likely the created PR object), error scenarios, or side effects. Adequate but not comprehensive.

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 coverage is 100% and each property has a description. The description adds no new meaning beyond 'Specify source and target branches, title, and body,' which partially echoes schema labels. Baseline is 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 clearly states the tool's purpose: 'Create a pull request in a GitHub repository.' It specifies the verb ('create'), the resource ('pull request'), and the key parameters (source/target branches, title, body). This distinguishes it from sibling tools like github_create_issue.

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 does not explicitly state when to use this tool versus alternatives. It only describes what it does. The context implies it is for creating pull requests, but lacks guidance on when not to use it or mention of alternative tools like github_create_issue.

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