Skip to main content
Glama
Sign In
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_change_request

[Code Management] Create a new change request (merge request). Supports specifying source/target branches, reviewers, associated work items, and optional AI review trigger.

Instructions

[Code Management] Create a new change request (merge request). Supports specifying source/target branches, reviewers, associated work items, and optional AI review trigger.

Input Schema

NameRequiredDescriptionDefault
titleYes标题，不超过256个字符。示例：'mr title' 或 '修复登录bug'
createFromNo创建来源。WEB - 页面创建（默认）WEB
descriptionNo描述，不超过10000个字符。示例：'mr description' 或 '修复了用户登录时的验证逻辑问题'
workItemIdsNo关联工作项ID列表，以字符串形式逗号分隔。示例值：722200214032b6b31e6f1434ab,xxx
repositoryIdYes代码库ID或全路径(斜杠须编码为%2F)，如 2835387 或 myorg%2FmyRepo
sourceBranchYes源分支名称，即要合并的分支。示例：'demo-branch' 或 'feature/user-login'
targetBranchYes目标分支名称，即合并到的分支。示例：'master' 或 'main'
organizationIdYes组织ID
extensionParamsNo扩展参数，值必须为字符串。aiReview.model 用于指定 AI 评审模型，值为 JSON 字符串，例如 {"modelKey":"glm-5.2"}
reviewerUserIdsNo评审人用户ID列表。示例：['62c795xxxb468af8'] 或 ['62c795xxxb468af8', '62c795xxxb468af9']
sourceProjectIdNo源库ID，如果未提供，将尝试自动获取。示例：2813489
targetProjectIdNo目标库ID，如果未提供，将尝试自动获取。示例：2813489
triggerAIReviewRunNo是否触发AI评审。true - 触发AI评审；false - 不触发（默认）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.68
    • addedInput schema / properties / extensionParams
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "扩展参数，值必须为字符串。aiReview.model 用于指定 AI 评审模型，值为 JSON 字符串，例如 {\"modelKey\":\"glm-5.2\"}",
+  "type": "object"
+}
  2. Changed4 schema fields changedv0.3.60
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / organizationId / description
      Previous value: -"组织ID，可在组织管理后台的基本信息页面获取。示例：'60d54f3daccf2bbd6659f3ad'"New value: +"组织ID"
    • changedInput schema / properties / repositoryId / description
      Previous value: -"代码库ID或者URL-Encoder编码的全路径。示例：'2835387' 或 '60de7a6852743a5162b5f957%2FDemoRepo'（注意：斜杠需要URL编码为%2F）"New value: +"代码库ID或全路径(斜杠须编码为%2F)，如 2835387 或 myorg%2FmyRepo"
    • changedInput schema / properties / repositoryId / type
      Previous value: -"string"New value: +[
+  "string",
+  "number"
+]
  3. Changed2 schema fields changedv0.3.44
    • changedInput schema / properties / createFrom / description
      Previous value: -"创建来源。WEB - 页面创建；COMMAND_LINE - 命令行创建。默认为WEB"New value: +"创建来源。WEB - 页面创建（默认）"
    • changedInput schema / properties / createFrom / enum
      Previous value: -[
-  "WEB",
-  "COMMAND_LINE"
-]New value: +[
+  "WEB"
+]
  4. Changed20 schema fields changedv0.3.35
    • changedInput schema / properties / createFrom / description
      Previous value: -"Creation source. Possible values: WEB (created from web page), COMMAND_LINE (created from command line). Default is WEB"New value: +"创建来源。WEB - 页面创建；COMMAND_LINE - 命令行创建。默认为WEB"
    • addedInput schema / properties / createFrom / enum
      Added value: +[
+  "WEB",
+  "COMMAND_LINE"
+]
    • addedInput schema / properties / description / anyOf
      Added value: +[
+  {
+    "maxLength": 10000,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / description / description
      Previous value: -"Description, no more than 10000 characters"New value: +"描述，不超过10000个字符。示例：'mr description' 或 '修复了用户登录时的验证逻辑问题'"
    • removedInput schema / properties / description / type
      Removed value: -[
-  "string",
-  "null"
-]
    • changedInput schema / properties / organizationId / description
      Previous value: -"Organization ID, can be found in the basic information page of the organization admin console"New value: +"组织ID，可在组织管理后台的基本信息页面获取。示例：'60d54f3daccf2bbd6659f3ad'"
    • changedInput schema / properties / repositoryId / description
      Previous value: -"Repository ID or a combination of organization ID and repository name, for example: 2835387 or organizationId%2Frepo-name (Note: slashes need to be URL encoded as %2F)"New value: +"代码库ID或者URL-Encoder编码的全路径。示例：'2835387' 或 '60de7a6852743a5162b5f957%2FDemoRepo'（注意：斜杠需要URL编码为%2F）"
    • changedInput schema / properties / reviewerUserIds / description
      Previous value: -"Reviewer user ID list"New value: +"评审人用户ID列表。示例：['62c795xxxb468af8'] 或 ['62c795xxxb468af8', '62c795xxxb468af9']"
    • changedInput schema / properties / sourceBranch / description
      Previous value: -"Source branch name"New value: +"源分支名称，即要合并的分支。示例：'demo-branch' 或 'feature/user-login'"
    • changedInput schema / properties / sourceProjectId / description
      Previous value: -"Source repository ID (if not provided, will try to get automatically)"New value: +"源库ID，如果未提供，将尝试自动获取。示例：2813489"
    • changedInput schema / properties / sourceProjectId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / targetBranch / description
      Previous value: -"Target branch name"New value: +"目标分支名称，即合并到的分支。示例：'master' 或 'main'"
    • changedInput schema / properties / targetProjectId / description
      Previous value: -"Target repository ID (if not provided, will try to get automatically)"New value: +"目标库ID，如果未提供，将尝试自动获取。示例：2813489"
    • changedInput schema / properties / targetProjectId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / title / description
      Previous value: -"Title, no more than 256 characters"New value: +"标题，不超过256个字符。示例：'mr title' 或 '修复登录bug'"
    • addedInput schema / properties / title / maxLength
      Added value: +256
    • changedInput schema / properties / triggerAIReviewRun / description
      Previous value: -"Whether to trigger AI review, default is false"New value: +"是否触发AI评审。true - 触发AI评审；false - 不触发（默认）"
    • removedInput schema / properties / workItemIds / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / workItemIds / description
      Previous value: -"Associated work item ID list"New value: +"关联工作项ID列表，以字符串形式逗号分隔。示例值：722200214032b6b31e6f1434ab,xxx"
    • addedInput schema / properties / workItemIds / type
      Added value: +"string"
  5. First observedv1.0.0

TDQS

C2.9/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 behavioral burden. For a mutation tool, it says nothing about required permissions, whether the CR is created as draft/open, what state it lands in, whether reviewers must already be org members, or any side effects of triggerAIReviewRun—all significant gaps.

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?

A single tightly-scoped sentence plus a bracketed category tag; front-loads the verb and resource with no wasted clauses. Efficient and well-structured, though the '[Code Management]' prefix is low-value padding.

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?

For a 13-parameter mutation tool with no annotations and no output schema, the description is thin on operational context. Relying on 100% schema coverage is reasonable, but it omits permissions, creation state, and merge/AI-review side effects an agent would need.

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 description coverage is 100%, so the schema already documents every parameter including examples and defaults. The description only restates the categories (branches, reviewers, work items, AI review) without adding format or syntax detail, so the baseline of 3 applies.

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?

States a specific verb+resource ('Create a new change request (merge request)') and enumerates the capabilities it supports. The agent can distinguish it from update_change_request, merge_change_request, and review_change_request by the 'create new' verb, though the description never explicitly names those siblings.

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?

No when-to-use or when-not-to-use guidance. It lists supported features (branches, reviewers, work items, AI review) but never tells the agent under what conditions to invoke this versus update_change_request or review_change_request, nor any prerequisites before creating a CR.

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

Deploy Server

Other Tools