Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_change_request_comments

List comments on a change request, filtering by type (global or inline), state (opened or draft), resolved status, and file path.

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
organizationIdYes组织ID,可在组织管理后台的基本信息页面获取。示例:'60d54f3daccf2bbd6659f3ad'
repositoryIdYes代码库ID或者URL-Encoder编码的全路径。示例:'2835387' 或 '60de7a6852743a5162b5f957%2FDemoRepo'(注意:斜杠需要URL编码为%2F)
localIdYes合并请求局部ID,表示代码库中第几个合并请求。示例:'1' 或 '42'
patchSetBizIdsNo关联版本ID列表,每个评论都关联一个版本,表示该评论是在哪个版本上发布的。对于全局评论,关联的是最新合并源版本。示例:['bf117304dfe44d5d9b1132f348edf92e', '537367017a9841738ac4269fbf6aacbe']
commentTypeNo评论类型。GLOBAL_COMMENT - 全局评论;INLINE_COMMENT - 行内评论GLOBAL_COMMENT
stateNo评论状态。OPENED - 已发布的评论;DRAFT - 草稿评论OPENED
resolvedNo是否已解决。true - 只查询已解决的评论;false - 只查询未解决的评论(默认值)
filePathNo文件路径过滤,仅用于行内评论。可以过滤特定文件的评论。示例:'/src/main/java/com/example/MyClass.java' 或 'src/utils/helper.ts'
Behavior2/5

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

No annotations are provided; the description does not disclose whether the tool is read-only, requires specific permissions, or has side effects. It only describes functionality, leaving behavioral traits unclear.

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 with a brief list of filters, front-loading the purpose and key details without extraneous words.

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?

The description omits mention of several parameters (e.g., patchSetBizIds) and does not cover required parameters or output behavior, leaving gaps for an agent to fully understand the tool's capabilities.

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 the schema already documents all parameters. The description repeats some filter options but does not add significant meaning beyond the schema's descriptions.

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 action ('List comments') and resource ('change request'), specifies the domain ('Code Management'), and enumerates supported filters, distinguishing it from sibling tools like list_work_item_comments.

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?

The description mentions filtering options, implying when to use the tool (when you need to list comments with filters), but does not explicitly state when not to use it or mention alternative tools for other types of comments.

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