Skip to main content
Glama

create_pr

Create a GitHub Pull Request without AI code review. You supply the title and description.

Instructions

Creates a Pull Request on GitHub WITHOUT AI review. RECOMMENDED WORKFLOW: (1) Call 'generate_pr_title' → get prompt, (2) YOU analyze and generate title, (3) Call 'generate_pr_description' → get prompt, (4) YOU analyze and generate description, (5) Call THIS tool with 'title' and 'description' parameters. If not provided, simple versions are auto-generated from commits/templates. NOTE: This tool does NOT include AI code review. For complete PR WITH AI review, use 'create_pr_complete' instead. This tool: analyzes branch, creates/updates PR, adds reviewers automatically. Requires GITHUB_TOKEN. Use when user asks to create a simple PR without code review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNoCreate the PR as a draft
titleNoRECOMMENDED: YOUR (Claude's) generated PR title. Workflow: (1) Call 'generate_pr_title' to get analysis prompt, (2) YOU analyze and create intelligent title, (3) Pass YOUR title here. DO NOT pass the tool's output directly - it's a prompt for YOU, not the final title. If not provided, a simple title is auto-generated from commit messages.
languageNoDescription languagefr
templateNoTemplate to use for the descriptionstandard
baseBranchNoBase branch for comparison (auto-detected if not provided)
descriptionNoRECOMMENDED: YOUR (Claude's) generated PR description. Workflow: (1) Call 'generate_pr_description' to get analysis prompt, (2) YOU analyze and write intelligent description, (3) Pass YOUR description here. DO NOT pass the tool's output directly - it's a prompt for YOU, not the final description. If not provided, a simple template-based description is auto-generated.
githubTokenNoGitHub token for authentication (optional, defaults to GITHUB_TOKEN env var)
addReviewersNoAutomatically suggest and add reviewers based on Git history
includeStatsNoInclude statistics in the description
maxReviewersNoMaximum number of reviewers to add (1-20)
maxTitleLengthNoMaximum length for the title (optional, e.g., 72)
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behaviors: no AI review, branch analysis, auto-update, automatic reviewer addition, and token requirement. Update behavior could be clearer.

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 well-structured with workflow steps and notes, but somewhat verbose. Every sentence earns its place, though some repetition exists (e.g., 'RECOMMENDED' emphasis).

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?

Given 11 parameters and no output schema, the description comprehensively covers the workflow, auto-generation fallback, and sibling distinction. It could explicitly mention what the tool returns (e.g., PR object) but is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 11 parameters have schema coverage, but the description adds extensive workflow context (e.g., how to use title/description parameters, guidance on NOT passing tool output directly) that significantly enhances understanding beyond the schema.

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 'Creates a Pull Request on GitHub WITHOUT AI review', uses specific verbs and resource, and explicitly distinguishes from sibling 'create_pr_complete'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a step-by-step RECOMMENDED WORKFLOW, explicitly tells when to use this tool vs 'create_pr_complete', and advises against passing tool outputs directly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/valentin-harrang/pr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server