Skip to main content
Glama
yjiace

AlibabaCloud DevOps MCP Server

by yjiace

search_projects

Search for Yunxiao project lists to find projects you manage, participate in, or have created, using filters like name, status, creation date, and administrator.

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, so the description carries full burden. It mentions the tool searches for projects but doesn't disclose key behavioral traits: whether it's read-only (implied by 'search'), pagination behavior (though parameters exist), rate limits, authentication needs, or what the output looks like (no output schema). For a search tool with 16 parameters and no annotations, this is insufficient.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, but the use cases are somewhat redundant (they restate the search intent). It's concise (three sentences), but the structure could be improved by integrating use cases more naturally or adding critical context. It's adequate but not optimally structured.

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?

Given the tool's complexity (16 parameters, no annotations, no output schema), the description is incomplete. It lacks information on output format, error handling, pagination details (beyond parameters), and how to interpret results. For a search tool in a project management context, this leaves significant 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?

Schema description coverage is 100%, so the schema fully documents all 16 parameters. The description adds no parameter-specific information beyond the schema (e.g., it doesn't explain how 'scenarioFilter' relates to the use cases). Baseline 3 is appropriate when the schema does all the work, but the description doesn't enhance understanding of complex parameters like 'advancedConditions'.

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 the tool's purpose: 'Search for Yunxiao Project List' with the verb 'search' and resource 'Project List'. It distinguishes projects from repositories, adding domain context. However, it doesn't explicitly differentiate from sibling search tools like 'search_workitems' or 'search_app_tags', which keeps it from a perfect score.

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 provides two use cases ('Query projects I am involved in' and 'Query projects I have created'), which imply usage scenarios. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'get_project' for a single project or other search tools), and doesn't mention prerequisites like needing organizationId. This is adequate but has gaps.

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/yjiace/alibabacloud-devops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server