Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

search_projects

Search for projects in an organization using filters like name, status, dates, creator, or admin. Query projects you manage, participate in, or have favorited with pagination.

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 exist, so the description must carry the full burden. It states 'Search' implying read-only, but does not explicitly confirm no side effects, rate limits, or other behavioral traits. No mention of pagination behavior or handling of empty results.

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?

Relatively concise, with a helpful definition of 'project' and two use cases. The bracket prefix '[Project Management]' is unnecessary but not harmful. It could be more structured (e.g., bullet points for use cases).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters and no output schema, the description is insufficient. It omits explanations of complex parameters (scenarioFilter, extraConditions) and does not clarify how to combine filters. The two use cases are too simplistic for the tool's capabilities.

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?

All 16 parameters have schema descriptions (100% coverage). The description adds no extra semantic value beyond the schema, e.g., it does not explain how scenarioFilter relates to the use cases or how to properly construct extraConditions. Baseline score applies due to high coverage.

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 a project list and distinguishes projects from code repositories. However, it does not differentiate from sibling tools like get_project (single project retrieval) or search_workitems (searching for work items), leaving ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Only two use cases are given ('projects I am involved in' and 'projects I have created'), but no guidance on when to use this tool versus alternatives like get_project or search_programs. No exclusions or context-specific conditions are provided.

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