Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

create_change_request_comment

Post comments on merge requests, including global feedback on the entire request or inline notes on specific code lines. Provide file path and line numbers for targeted code review discussions.

Instructions

[Code Management] Create a comment on a change request. Supports two types: GLOBAL_COMMENT (global comment on the entire merge request) and INLINE_COMMENT (inline comment on specific code lines). For INLINE_COMMENT, you must provide file_path, line_number, from_patchset_biz_id, and to_patchset_biz_id parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNo是否草稿评论。true - 草稿评论（不会立即显示给其他人）；false - 正式评论（默认值）
contentYes评论内容，长度必须在 1 到 65535 之间。示例：'This is a comment content.' 或 '这里需要优化性能，建议使用缓存机制'
localIdYes局部ID，表示代码库中第几个合并请求。示例：'1' 或 '42'
resolvedNo是否标记已解决。true - 已解决；false - 未解决（默认值）
file_pathNo文件路径，仅行内评论需要。表示评论针对的文件路径。示例：'/src/main/java/com/example/MyClass.java' 或 'src/utils/helper.ts' 或 'frontend/components/Button.tsx'
line_numberNo行号，仅行内评论需要，从1开始计数（示例：42 表示第42行）。全局评论可省略，或传 0 / null 表示无行号
comment_typeNo评论类型。GLOBAL_COMMENT - 全局评论（对整个合并请求的评论）；INLINE_COMMENT - 行内评论（针对特定代码行的评论）。创建行内评论时，必须提供 file_path、line_number、from_patchset_biz_id 和 to_patchset_biz_id 参数GLOBAL_COMMENT
repositoryIdYes代码库ID或全路径(斜杠须编码为%2F)，如 2835387 或 myorg%2FmyRepo
organizationIdYes组织ID
patchset_biz_idYes关联版本ID，具有唯一性。对于全局评论，使用最新合并源版本ID；对于行内评论，选择 from_patchset_biz_id 或 to_patchset_biz_id 中的一个。示例：'bf117304dfe44d5d9b1132f348edf92e'
to_patchset_biz_idNo比较的目标版本ID，行内评论类型必传。表示代码比较的目标版本（通常是源分支版本，即合并源对应的版本）。示例：'537367017a9841738ac4269fbf6aacbe'
from_patchset_biz_idNo比较的起始版本ID，行内评论类型必传。表示代码比较的起始版本（通常是目标分支版本，即合并目标对应的版本）。示例：'bf117304dfe44d5d9b1132f348edf92e'
parent_comment_biz_idNo父评论ID，用于回复评论。如果这是对某个评论的回复，需要传入被回复评论的 bizId。示例：'1d8171cf0cc2453197fae0e0a27d5ece'

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv0.3.60
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / line_number / anyOf
      Added value: +[
+  {
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / line_number / description
      Previous value: -"行号，仅行内评论需要。表示评论针对的代码行号，从1开始计数。示例：42 表示第42行，100 表示第100行"New value: +"行号，仅行内评论需要，从1开始计数（示例：42 表示第42行）。全局评论可省略，或传 0 / null 表示无行号"
    • removedInput schema / properties / line_number / exclusiveMinimum
      Removed value: -0
    • removedInput schema / properties / line_number / type
      Removed value: -"integer"
    • changedInput schema / properties / localId / type
      Previous value: -"string"New value: +[
+  "string",
+  "number"
+]
    • 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"
+]
  2. Changed23 schema fields changedv0.3.35
    • changedInput schema / properties / comment_type / description
      Previous value: -"Comment type. Possible values: GLOBAL_COMMENT, INLINE_COMMENT"New value: +"评论类型。GLOBAL_COMMENT - 全局评论（对整个合并请求的评论）；INLINE_COMMENT - 行内评论（针对特定代码行的评论）。创建行内评论时，必须提供 file_path、line_number、from_patchset_biz_id 和 to_patchset_biz_id 参数"
    • addedInput schema / properties / comment_type / enum
      Added value: +[
+  "GLOBAL_COMMENT",
+  "INLINE_COMMENT"
+]
    • changedInput schema / properties / content / description
      Previous value: -"Comment content, length must be between 1 and 65535"New value: +"评论内容，长度必须在 1 到 65535 之间。示例：'This is a comment content.' 或 '这里需要优化性能，建议使用缓存机制'"
    • addedInput schema / properties / content / maxLength
      Added value: +65535
    • addedInput schema / properties / content / minLength
      Added value: +1
    • changedInput schema / properties / draft / description
      Previous value: -"Whether it is a draft comment"New value: +"是否草稿评论。true - 草稿评论（不会立即显示给其他人）；false - 正式评论（默认值）"
    • changedInput schema / properties / file_path / description
      Previous value: -"File name, only for inline comments"New value: +"文件路径，仅行内评论需要。表示评论针对的文件路径。示例：'/src/main/java/com/example/MyClass.java' 或 'src/utils/helper.ts' 或 'frontend/components/Button.tsx'"
    • changedInput schema / properties / file_path / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / from_patchset_biz_id / description
      Previous value: -"Start version ID for comparison, required for INLINE_COMMENT type"New value: +"比较的起始版本ID，行内评论类型必传。表示代码比较的起始版本（通常是目标分支版本，即合并目标对应的版本）。示例：'bf117304dfe44d5d9b1132f348edf92e'"
    • changedInput schema / properties / from_patchset_biz_id / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / line_number / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / line_number / description
      Previous value: -"Line number, only for inline comments"New value: +"行号，仅行内评论需要。表示评论针对的代码行号，从1开始计数。示例：42 表示第42行，100 表示第100行"
    • addedInput schema / properties / line_number / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / line_number / type
      Added value: +"integer"
    • changedInput schema / properties / localId / description
      Previous value: -"Local ID, represents the nth merge request in the repository"New value: +"局部ID，表示代码库中第几个合并请求。示例：'1' 或 '42'"
    • 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 / parent_comment_biz_id / description
      Previous value: -"Parent comment ID"New value: +"父评论ID，用于回复评论。如果这是对某个评论的回复，需要传入被回复评论的 bizId。示例：'1d8171cf0cc2453197fae0e0a27d5ece'"
    • changedInput schema / properties / parent_comment_biz_id / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / patchset_biz_id / description
      Previous value: -"Associated version ID, if it's INLINE_COMMENT, choose one from from_patchset_biz_id or to_patchset_biz_id"New value: +"关联版本ID，具有唯一性。对于全局评论，使用最新合并源版本ID；对于行内评论，选择 from_patchset_biz_id 或 to_patchset_biz_id 中的一个。示例：'bf117304dfe44d5d9b1132f348edf92e'"
    • 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 / resolved / description
      Previous value: -"Whether to mark as resolved"New value: +"是否标记已解决。true - 已解决；false - 未解决（默认值）"
    • changedInput schema / properties / to_patchset_biz_id / description
      Previous value: -"Target version ID for comparison, required for INLINE_COMMENT type"New value: +"比较的目标版本ID，行内评论类型必传。表示代码比较的目标版本（通常是源分支版本，即合并源对应的版本）。示例：'537367017a9841738ac4269fbf6aacbe'"
    • changedInput schema / properties / to_patchset_biz_id / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the two comment modes and parameter requirements, but does not mention permissions, side effects, or draft behavior. This is adequate but not rich.

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?

The description is two sentences, front-loaded with a context tag, and packs essential information about types and required parameters with no waste.

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 the tool's complexity (13 params, two types, no output schema), the description covers the key decision of comment type and its prerequisites. It doesn't explain every optional parameter, but the schema covers those, making it sufficient for correct invocation.

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. The description adds a useful grouping of inline-only parameters, but the schema already provides detailed semantics for each parameter. No significant additional meaning 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 states a specific verb+resource: 'Create a comment on a change request.' It further distinguishes between GLOBAL_COMMENT and INLINE_COMMENT, which clarifies scope and differentiates from sibling tools like create_commit_comment.

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 context on when to use each comment type and explicitly lists the required parameters for INLINE_COMMENT. However, it does not explicitly mention alternatives or when-not-to-use scenarios relative to sibling tools.

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/aliyun/alibabacloud-devops-mcp-server'

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