Skip to main content
Glama
yumeminami

Git MCP Server

by yumeminami
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_merge_request

Create a merge request with cross-project support on GitHub and GitLab. Specify source and target branches, assignee, and description.

Instructions

Create a new merge request with cross-project support

Args: platform: Git platform name (github, gitlab, etc.) project_id: Source project ID (for cross-project MRs) or project ID (for same-project MRs) title: Merge request title source_branch: Source branch name or 'owner:branch' format for cross-repo target_branch: Target branch name (default: 'main') description: Optional merge request description assignee: Optional assignee username target_project_id: Optional target project ID for cross-project merge requests **kwargs: Additional platform-specific parameters

Returns: Dict containing merge request details

Examples: # Same-project MR create_merge_request("gitlab", "123", "Fix bug", "feature-branch", "main")

# Cross-project MR (fork to upstream)
create_merge_request("gitlab", "456", "Fix bug", "feature-branch", "main",
                   target_project_id="123")

# GitHub cross-repo PR (using branch format)
create_merge_request("github", "upstream/repo", "Fix bug", "fork-owner:feature-branch", "main")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
kwargsYes
assigneeNo
platformYes
milestoneNo
project_idYes
descriptionNo
source_branchYes
target_branchNomain
target_project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It explains cross-project support and branch format but does not disclose authentication requirements, rate limits, or potential errors. Return type is minimally described as 'Dict containing merge request details'.

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 Args, Returns, and Examples sections, but is slightly lengthy. However, each part adds value and no sentences are wasted.

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 10 parameters, cross-project support, and no annotations, the description is fairly complete. It covers parameter details, examples, and usage distinctions. Output schema exists but description provides only minimal return info.

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?

Schema description coverage is 0%, so description must and does fully explain parameters. It adds context like 'owner:branch' format for source_branch, kwargs for platform-specific parameters, and examples for each use case.

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 'Create a new merge request with cross-project support' with specific verb and resource. Examples distinguish this tool from siblings like update_merge_request or list_merge_requests.

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

Usage Guidelines4/5

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

The description provides clear usage contexts through examples for same-project and cross-project merge requests, and explains parameter differences. However, it does not explicitly state when not to use this tool versus alternatives.

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/yumeminami/git_mcp'

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