Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_change_requests

Find and filter change requests by repository, author, reviewer, state, keyword, or creation time, with pagination and sorting.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
  2. Changed16 schema fields changedv0.3.35
    • changedInput schema / properties / authorIds / description
      Previous value: -"Creator user ID list, multiple separated by commas"New value: +"创建者用户ID列表，多个以逗号分隔。示例：'62c795xxxb468af8' 或 '62c795xxxb468af8,62c795xxxb468af9'"
    • changedInput schema / properties / createdAfter / description
      Previous value: -"End creation time, time format is ISO 8601, for example: 2019-03-15T08:00:00Z"New value: +"截止创建时间，时间格式为ISO 8601。查询创建时间不晚于此时间的合并请求。示例：'2024-04-05T15:30:45Z'"
    • changedInput schema / properties / createdBefore / description
      Previous value: -"Start creation time, time format is ISO 8601, for example: 2019-03-15T08:00:00Z"New value: +"起始创建时间，时间格式为ISO 8601。查询创建时间不早于此时间的合并请求。示例：'2024-04-05T15:30:45Z'"
    • changedInput schema / properties / orderBy / description
      Previous value: -"Sort field. Possible values: created_at (creation time), updated_at (update time, default)"New value: +"排序字段。created_at - 按创建时间排序；updated_at - 按更新时间排序（默认）。示例：'updated_at'"
    • addedInput schema / properties / orderBy / enum
      Added value: +[
+  "created_at",
+  "updated_at"
+]
    • 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 / page / description
      Previous value: -"Page number"New value: +"页码，从1开始。示例：1"
    • changedInput schema / properties / perPage / description
      Previous value: -"Items per page"New value: +"每页大小，默认20。示例：20"
    • changedInput schema / properties / projectIds / description
      Previous value: -"Repository ID or a combination of organization ID and repository name list, for example: 2835387 or organizationId%2Frepo-name (Note: slashes need to be URL encoded as %2F), multiple separated by commas"New value: +"代码库ID或者路径列表，多个以逗号分隔。示例：'2813489,2813490' 或 '2813489,60de7a6852743a5162b5f957%2FDemoRepo'（注意：斜杠需要URL编码为%2F）"
    • changedInput schema / properties / reviewerIds / description
      Previous value: -"Reviewer user ID list, multiple separated by commas"New value: +"评审人用户ID列表，多个以逗号分隔。示例：'62c795xxxb468af8' 或 '62c795xxxb468af8,62c795xxxb468af9'"
    • changedInput schema / properties / search / description
      Previous value: -"Title keyword search"New value: +"标题关键字搜索，用于在合并请求标题中搜索。示例：'mr title' 或 'bug fix'"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order. Possible values: asc (ascending), desc (descending, default)"New value: +"排序方式。asc - 升序；desc - 降序（默认）。示例：'desc'"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "asc",
+  "desc"
+]
    • addedInput schema / properties / state / anyOf
      Added value: +[
+  {
+    "enum": [
+      "opened",
+      "merged",
+      "closed"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / state / description
      Previous value: -"Merge request filter status. Possible values: opened, merged, closed. Default is null, which queries all statuses"New value: +"合并请求筛选状态。opened - 已开启；merged - 已合并；closed - 已关闭。默认为null，即查询全部状态。示例：'opened'"
    • removedInput schema / properties / state / type
      Removed value: -[
-  "string",
-  "null"
-]
  3. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

There are no annotations, so the description carries the burden. It mentions functional capabilities (filtering, pagination, sorting) but does not disclose side effects, authentication requirements, or return format. For a list operation it is reasonable 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 concise, two sentences, front-loaded with the core purpose, and efficiently lists key features without redundancy.

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?

With 12 parameters, no output schema, and no annotations, the description covers the main capabilities but omits details on return structure, error handling, or limits. It is adequate for a standard list tool but leaves some gaps.

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% and each parameter has detailed descriptions. The description adds a high-level summary of filter categories (repository, author, reviewer, etc.) that mirrors the schema definitions, offering marginal added value over 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 clearly states 'List change requests' with verb+resource, and distinguishes from siblings like get_change_request and create_change_request. It also lists supported features (filtering, pagination, sorting) that set it apart.

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 listing change requests with filters, but does not explicitly contrast with single-fetch get_change_request or other alternatives. It provides clear context but lacks explicit when-not guidance.

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