React Development Workflow MCP Server

merge_pull_request

Merge a pull request for a branch, select a merge strategy (squash, merge, rebase), and optionally delete the branch after merging.

Instructions

Merge 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": {
      "branchName": "<branchName>"
    },
    "name": "merge_pull_request"
  }
}

Input Schema

Name	Required	Description
`branchName`	Yes	Branch to merge
`mergeStrategy`	No	Merge strategy
`deleteAfterMerge`	No	Delete branch after merge

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

C2.8/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 of behavioral disclosure. It simply states 'Merge a pull request' without disclosing that this is a write/destructive operation, whether the branch is deleted by default, or any side effects. The meaning of mergeStrategy and deleteAfterMerge is left entirely to the schema.

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

Conciseness3/5

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

The description is extremely concise and front-loaded, but it essentially restates the tool name without adding value. It is not poorly structured, but it lacks the richness expected to make every word informative.

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?

This is a mutation tool with no annotations and no output schema, so the description needs to provide more context. It omits behavior around merge strategies, branch deletion, failure conditions, and the meaning of the return value, making the tool under-specified for an agent to use confidently.

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 already describes all three parameters with 100% coverage, so the schema provides the parameter meaning. The description adds no additional context about how branchName, mergeStrategy, or deleteAfterMerge are used, but it does not need to compensate because the schema is complete.

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?

The description 'Merge a pull request' clearly states the action and target resource. It is not vague, but it does not add any information beyond what the tool name already implies, and it does not mention that the merge is identified by a branch name or distinguish it from sibling tools beyond the verb.

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 versus alternatives like create_pull_request or check_pr_status. No prerequisites, exclusions, or conditions are provided, leaving the agent to infer usage solely from the tool name.

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

Deploy Server