Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

search_projects

Search for Yunxiao projects using filters like name, status, creator, and creation date. Supports predefined scenarios to find projects you manage, participate in, or have favorited.

Instructions

[Project Management] Search for Yunxiao Project List. A Project is a project management unit that includes work items and sprints, and it is different from a code repository (Repository).

Use Cases:

Query projects I am involved in Query projects I have created

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
nameNoText contained in project name
statusNoProject status ID, multiple separated by commas
createdAfterNoCreated not earlier than, format: YYYY-MM-DD
createdBeforeNoCreated not later than, format: YYYY-MM-DD
creatorNoCreator
adminUserIdNoProject administrator user ID, should use userId returned from getCurrentOrganizationInfoFunc or user-provided user ID, multiple IDs separated by commas
logicalStatusNoLogical status, e.g., NORMAL
scenarioFilterNoPredefined filter scenarios: 'manage' (projects I manage), 'participate' (projects I participate in), 'favorite' (projects I favorited). Will be used to construct appropriate extraConditions. Requires userId from getCurrentOrganizationInfoFunc.
userIdNoUser ID to use with scenarioFilter, should be the userId returned from getCurrentOrganizationInfoFunc
advancedConditionsNoAdvanced filter conditions, JSON format
extraConditionsNoAdditional filter conditions as JSON string. Should be constructed similar to the conditions parameter. For common scenarios: 1) For 'projects I manage': use fieldIdentifier 'project.admin' with the user ID; 2) For 'projects I participate in': use fieldIdentifier 'users' with the user ID; 3) For 'projects I favorited': use fieldIdentifier 'collectMembers' with the user ID. Example: JSON.stringify({conditionGroups:[[{className:'user',fieldIdentifier:'project.admin',format:'multiList',operator:'CONTAINS',value:[userId]}]]})
orderByNoSort field, default is gmtCreate, supports: gmtCreate (creation time), name (name)gmtCreate
pageNoPagination parameter, page number
perPageNoPagination parameter, page size, 0-200, default value is 20
sortNoSort order, default is desc, options: desc (descending), asc (ascending)desc
Behavior2/5

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

No annotations are provided, and the description does not explicitly state that this is a read-only operation. It implies a list/search action but lacks disclosure of side effects, permissions, or rate limits.

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 concise and front-loaded with purpose and use cases. It avoids redundant details, though could be slightly more structured.

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 16 parameters and complete schema coverage, the description provides sufficient context for typical use cases. It lacks explicit mention of output format, but schema covers pagination.

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% with descriptions. The description adds value by explaining scenarioFilter, extraConditions, and userId usage for common scenarios, beyond what the schema alone provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches for projects, distinguishes from code repositories, and lists use cases. It differentiates from sibling tools like get_project and search_programs.

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?

Use cases are provided (query projects I am involved in or created), but no explicit guidance on when to use this tool versus alternatives like get_project or search_workitems. The context is implied but not explicit.

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