mcp-magento-cloud

create_branch

Create a new environment branch in your Magento Cloud project by cloning the integration environment. Provide a project ID and branch name to set up development or testing environments.

Instructions

Create a new environment branch from integration. The new branch will be a clone of the integration environment.

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": {
      "project": "<project>",
      "branch_name": "<branch_name>"
    },
    "name": "create_branch"
  }
}

Input Schema

Name	Required	Description
`title`	No	Human-readable title for the branch. Defaults to the branch name if not provided.
`project`	Yes	The Magento Cloud project ID
`branch_name`	Yes	The branch name (ID) for the new environment, e.g. 'feature-xyz', 'bugfix-123'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided. Description only says branch is a clone of integration, but fails to disclose permissions needed, response behavior, or side effects. Minimal behavioral disclosure.

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?

Two succinct sentences, no wasted words. Efficiently conveys core purpose.

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?

No output schema, so description should clarify return value or side effects. It does not. Also missing prerequisites or contextual cues like typical use cases.

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%, so baseline is 3. Description adds context that the branch is a clone, but does not elaborate on the 'title' parameter or provide constraints beyond 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?

States verb 'Create', resource 'environment branch', and source 'integration'. Clearly distinguishes from siblings like 'push_branch' or 'list_environments'.

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?

Implied usage for creating a new branch from integration, but no explicit when-to-use or when-not-to-use, nor any mention of alternatives among siblings.

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

Deploy Server