Skip to main content
Glama
yjiace

AlibabaCloud DevOps MCP Server

by yjiace

list_pipelines

Retrieve and filter pipelines in an organization by creation time, execution time, name, status, and pagination options for pipeline management.

Instructions

[Pipeline Management] Get a list of pipelines in an organization with filtering options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID, can be found in the basic information page of the organization admin console
createStartTimeNoCreation start time in milliseconds timestamp format (e.g., 1729178040000). For filtering pipelines created after this time.
createEndTimeNoCreation end time in milliseconds timestamp format (e.g., 1729178040000). For filtering pipelines created before this time.
executeStartTimeNoExecution start time in milliseconds timestamp format (e.g., 1729178040000). For filtering pipelines executed after this time.
executeEndTimeNoExecution end time in milliseconds timestamp format (e.g., 1729178040000). For filtering pipelines executed before this time.
pipelineNameNoPipeline name for filtering
statusListNoPipeline status list, comma separated (SUCCESS,RUNNING,FAIL,CANCELED,WAITING)
perPageNoNumber of items per page, default 10, max 30
pageNoPage number, default 1
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 states it's a read operation ('Get a list'), which is clear, but lacks details on permissions, rate limits, pagination behavior, or what happens with no results. For a tool with 9 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.

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core purpose ('Get a list of pipelines'). It includes a category tag ('[Pipeline Management]') and key feature ('with filtering options') without unnecessary words.

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 tool's complexity (9 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose but lacks behavioral context, usage guidelines, and output details, making it minimally viable but incomplete for effective agent use.

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 parameters. The description adds minimal value by mentioning 'filtering options', which aligns with the schema but doesn't provide additional syntax or format details beyond what's already covered.

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 verb ('Get a list') and resource ('pipelines in an organization'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'smart_list_pipelines' or 'list_pipeline_runs', which prevents 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 Guidelines2/5

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

The description provides minimal guidance with 'with filtering options' but lacks explicit when-to-use instructions, prerequisites, or alternatives. It doesn't mention when to choose this over 'smart_list_pipelines' or other list tools, leaving usage unclear.

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