Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

search_programs

Search for programs (project sets) using filters such as name, status, and creator to manage and coordinate large projects.

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
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 of behavioral disclosure. It implies a read-only search operation but does not explicitly state behavior like pagination, sorting, or return format. The schema details are not repeated in the text, leaving some behavioral traits implicit.

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 relatively concise with a definition and bulleted use cases. It is front-loaded with the purpose. The definition of 'Program' adds value but could be slightly more terse.

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 11 parameters and no output schema, the description provides sufficient context: defines Program, lists filtering use cases, and hints at the response being a list. It is fairly complete for a search tool, though return structure is not described.

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 baseline is 3. The description adds no additional parameter details beyond the schema, but the use cases (e.g., query by name) help contextualize some parameters. No significant new semantics are provided.

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 it is for 'Search for Yunxiao Program (Project Set) List' and defines a Program as a collection of related projects. It distinguishes from sibling tools like search_projects and search_workitems by specifying the resource type.

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 lists three use cases (query by name, status, creator), providing clear context for when to use the tool. However, it does not explicitly mention when not to use it or alternatives among 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