Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_change_requests

List change requests with filtering by repository, author, reviewer, state, keywords, and creation time range. Supports pagination and sorting for efficient code management.

Instructions

[Code Management] List change requests with multi-condition filtering, pagination and sorting. Supports filtering by repository, author, reviewer, state (opened/merged/closed), search keywords, and creation time range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYes组织ID,可在组织管理后台的基本信息页面获取。示例:'60d54f3daccf2bbd6659f3ad'
pageNo页码,从1开始。示例:1
perPageNo每页大小,默认20。示例:20
projectIdsNo代码库ID或者路径列表,多个以逗号分隔。示例:'2813489,2813490' 或 '2813489,60de7a6852743a5162b5f957%2FDemoRepo'(注意:斜杠需要URL编码为%2F)
authorIdsNo创建者用户ID列表,多个以逗号分隔。示例:'62c795xxxb468af8' 或 '62c795xxxb468af8,62c795xxxb468af9'
reviewerIdsNo评审人用户ID列表,多个以逗号分隔。示例:'62c795xxxb468af8' 或 '62c795xxxb468af8,62c795xxxb468af9'
stateNo合并请求筛选状态。opened - 已开启;merged - 已合并;closed - 已关闭。默认为null,即查询全部状态。示例:'opened'
searchNo标题关键字搜索,用于在合并请求标题中搜索。示例:'mr title' 或 'bug fix'
orderByNo排序字段。created_at - 按创建时间排序;updated_at - 按更新时间排序(默认)。示例:'updated_at'updated_at
sortNo排序方式。asc - 升序;desc - 降序(默认)。示例:'desc'desc
createdBeforeNo起始创建时间,时间格式为ISO 8601。查询创建时间不早于此时间的合并请求。示例:'2024-04-05T15:30:45Z'
createdAfterNo截止创建时间,时间格式为ISO 8601。查询创建时间不晚于此时间的合并请求。示例:'2024-04-05T15:30:45Z'
Behavior2/5

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

No annotations are present, but the description does not explicitly state that the operation is read-only or disclose any behavioral traits like authentication requirements, rate limits, or pagination behavior beyond mentioning it.

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, front-loaded sentence that efficiently lists capabilities without extraneous information, achieving high conciseness.

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 (12 parameters, no output schema), the description covers all major filtering and sorting dimensions. However, it lacks mention of the required organizationId and does not describe the return format, which would aid completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by mapping natural language filter types (repository, author, reviewer, state, search, time range) to parameters, though it omits the required organizationId parameter and does not elaborate on format details.

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 'List change requests' with specific filtering, pagination, and sorting capabilities, distinguishing it from sibling tools like get_change_request (single retrieval) and create_change_request (creation).

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?

Usage is implied by the tool's name and listing nature, but no explicit when-to-use or when-not-to-use guidance is provided, e.g., versus using get_change_request for a single request or other list 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