Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_repositories

Retrieve a paginated list of CodeUp repositories for an organization, with sorting and search options.

Instructions

[Code Management] Get the CodeUp Repository List.

A Repository serves as a unit for managing source code and is distinct from a Project.

Use Case:

View my repositories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID, can be found in the basic information page of the organization admin console
pageNoPage number, default starts from 1, generally should not exceed 150 pages
perPageNoItems per page, default 20, value range [1, 100]
orderByNoSort field, options include {created_at, name, path, last_activity_at}, default is created_atcreated_at
sortNoSort order, options include {asc, desc}, default is descdesc
searchNoSearch keyword, used to fuzzy match repository paths
archivedNoWhether archived
Behavior2/5

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

With no annotations, the description must disclose behavior. It only states the basic action and omits key traits like pagination, sorting, and filtering parameters, which are critical for a list tool.

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

Conciseness5/5

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

The description is very concise: two sentences plus a use case. No fluff, front-loaded with category. Every sentence serves a purpose.

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 7-parameter schema and no output schema, the description is somewhat complete for a simple list tool but lacks behavior details (e.g., pagination, sorting) that could be mentioned briefly. It meets minimum viability.

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 7 parameters are documented in the input schema (100% coverage), so the description does not need to add parameter details. The description adds no extra semantic value beyond the schema.

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 retrieves a list of repositories and distinguishes repositories from projects. However, it does not differentiate from sibling list tools (e.g., list_branches) beyond 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 Guidelines3/5

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

The use case 'View my repositories' implies usage but does not specify when not to use or mention alternative tools. No exclusions or prerequisites are given.

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