Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

search_programs

Search for program lists by name, status, creator, or creation date to manage related projects collectively.

Instructions

[Project Management] Search for Yunxiao Program (Project Set) List. A Program is a collection of multiple related projects, used for unified management and coordination of large projects.

Use Cases:

Query programs by name Query programs by status Query programs by creator

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID, can be found in the basic information page of the organization admin console
nameNoName search (fuzzy matching)
statusNoStatus identifiers (supports multiple, separated by commas)
gmtCreateStartNoCreation time start (format: yyyy-MM-dd HH:mm:ss)
gmtCreateEndNoCreation time end (format: yyyy-MM-dd HH:mm:ss)
creatorNoCreator identifier (supports multiple, separated by commas)
usersNoUser identifiers (supports multiple, separated by commas, used for extraConditions)
pageNoPagination parameter, page number, default is 1
perPageNoPagination parameter, page size, 0-200, default is 20
orderByNoSort field, currently only supports name and creation time, default is gmtCreate. gmtCreate: creation time, name: namegmtCreate
sortNoSort order, default is desc. desc: descending, asc: ascendingdesc
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the tool as a search/list operation but does not explicitly state it is read-only, mention auth requirements, rate limits, or pagination behavior beyond what the schema provides. The description lacks details on side effects or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a concise paragraph followed by a bullet list. It is front-loaded with a clear title-like statement. However, it could be slightly more concise by trimming redundant phrasing.

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?

Given the tool has 11 parameters and no output schema, the description does not explain return values or cover all filtering capabilities (e.g., time range, sorting, pagination). It mentions only three use cases, leaving some context gaps for an AI agent.

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?

The schema has 100% coverage with descriptions for all parameters. The description adds only high-level use cases (query by name, status, creator) but does not provide additional meaning beyond the schema. Baseline score of 3 is appropriate given high schema coverage.

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 searches for Yunxiao Program (Project Set) List and defines what a program is, distinguishing it from siblings like search_projects or search_workitems. The verb 'search' and resource 'program' are specific, and use cases are provided.

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 lists use cases but does not provide explicit guidance on when to use this tool versus alternatives like search_projects or search_workitems. There is no mention of when not to use or how it differs from siblings.

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