Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

list_change_request_comments

Fetch comments on a change request. Filter by comment type, state, resolved status, and file path to find relevant feedback.

Instructions

[Code Management] List comments on a change request. Supports filtering by comment type (GLOBAL_COMMENT or INLINE_COMMENT), state (OPENED or DRAFT), resolved status, and file path (for inline comments).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNo评论状态。OPENED - 已发布的评论；DRAFT - 草稿评论OPENED
localIdYes合并请求局部ID，表示代码库中第几个合并请求。示例：'1' 或 '42'
filePathNo文件路径过滤，仅用于行内评论。可以过滤特定文件的评论。示例：'/src/main/java/com/example/MyClass.java' 或 'src/utils/helper.ts'
resolvedNo是否已解决。true - 只查询已解决的评论；false - 只查询未解决的评论（默认值）
commentTypeNo评论类型。GLOBAL_COMMENT - 全局评论；INLINE_COMMENT - 行内评论GLOBAL_COMMENT
repositoryIdYes代码库ID或全路径(斜杠须编码为%2F)，如 2835387 或 myorg%2FmyRepo
organizationIdYes组织ID
patchSetBizIdsNo关联版本ID列表，每个评论都关联一个版本，表示该评论是在哪个版本上发布的。对于全局评论，关联的是最新合并源版本。示例：['bf117304dfe44d5d9b1132f348edf92e', '537367017a9841738ac4269fbf6aacbe']

Schema Changelog

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

  1. Changed5 schema fields changedv0.3.60
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • 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. Changed14 schema fields changedv0.3.35
    • changedInput schema / properties / commentType / description
      Previous value: -"Comment type. Possible values: GLOBAL_COMMENT, INLINE_COMMENT"New value: +"评论类型。GLOBAL_COMMENT - 全局评论；INLINE_COMMENT - 行内评论"
    • addedInput schema / properties / commentType / enum
      Added value: +[
+  "GLOBAL_COMMENT",
+  "INLINE_COMMENT"
+]
    • changedInput schema / properties / filePath / description
      Previous value: -"Filter by file path (for inline comments)"New value: +"文件路径过滤，仅用于行内评论。可以过滤特定文件的评论。示例：'/src/main/java/com/example/MyClass.java' 或 'src/utils/helper.ts'"
    • changedInput schema / properties / filePath / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / localId / description
      Previous value: -"Change request local ID"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'"
    • removedInput schema / properties / patchSetBizIds / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / patchSetBizIds / description
      Previous value: -"Associated version ID list, each comment is associated with a version, indicating which version the comment was posted on, for global comments, it's associated with the latest merge source version"New value: +"关联版本ID列表，每个评论都关联一个版本，表示该评论是在哪个版本上发布的。对于全局评论，关联的是最新合并源版本。示例：['bf117304dfe44d5d9b1132f348edf92e', '537367017a9841738ac4269fbf6aacbe']"
    • addedInput schema / properties / patchSetBizIds / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / patchSetBizIds / type
      Added value: +"array"
    • 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 marked as resolved"New value: +"是否已解决。true - 只查询已解决的评论；false - 只查询未解决的评论（默认值）"
    • changedInput schema / properties / state / description
      Previous value: -"Comment state. Possible values: OPENED, DRAFT"New value: +"评论状态。OPENED - 已发布的评论；DRAFT - 草稿评论"
    • addedInput schema / properties / state / enum
      Added value: +[
+  "OPENED",
+  "DRAFT"
+]
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the filtering behavior and defaults (e.g., default state OPENED, default commentType GLOBAL_COMMENT) but does not mention pagination, ordering, or whether the tool returns both global and inline comments if no type is specified. The description is accurate but not exhaustive.

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 a single sentence, front-loaded with the tool's purpose, and lists filters concisely. No wasted words.

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?

The tool has 8 parameters with 100% schema coverage and no output schema. The description covers the main filtering capabilities and defaults, which is sufficient for a list operation. It could mention pagination or response format, but given the schema richness, it is reasonably complete.

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 all parameters. The description adds a brief summary of filters but does not add significant meaning beyond the schema. It mentions filePath is for inline comments, which is also in the schema. Baseline 3 is appropriate.

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 the tool lists comments on a change request, with a specific verb ('List') and resource ('comments on a change request'). It also enumerates the filtering dimensions (comment type, state, resolved status, file path), which distinguishes it from sibling tools like create_change_request_comment and update_change_request_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 implies usage for retrieving comments with optional filters, but does not explicitly state when to use this tool versus alternatives (e.g., list_work_item_comments for work items). It provides clear context on what it does but lacks explicit exclusions or alternative guidance.

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