Skip to main content
Glama
yjiace

AlibabaCloud DevOps MCP Server

by yjiace

create_pipeline_run

Execute a pipeline in Alibaba Cloud DevOps with configurable parameters including branch mode, environment variables, and repository settings for automated deployment workflows.

Instructions

[Pipeline Management] Run a pipeline with optional parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID, can be found in the basic information page of the organization admin console
pipelineIdYesPipeline ID to run
paramsNoPipeline run parameters in JSON string format. Can include: branchModeBranchs(array), envs(object), runningBranchs(object), runningTags(object), runningPipelineArtifacts(object), runningAcrArtifacts(object), runningPackagesArtifacts(object), comment(string), needCreateBranch(boolean), releaseBranch(string)
descriptionNoNatural language description of how to run the pipeline, e.g. 'Run pipeline using branch mode with branches main and develop'
branchesNoBranches to use in branch mode or specific branches for repositories
branchModeNoWhether to run in branch mode
releaseBranchNoSpecific release branch to use
createReleaseBranchNoWhether to create a release branch
environmentVariablesNoEnvironment variables for the pipeline run
repositoriesNoSpecific repository configurations
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a mutation (likely, given 'create' in name), what permissions are required, rate limits, or what happens on success/failure (e.g., returns a run ID). This leaves critical operational traits unspecified.

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 brief and front-loaded with the core action, but the bracketed '[Pipeline Management]' adds minimal value and could be omitted. It's efficient with no wasted sentences, though slightly under-specified given the tool's complexity.

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?

For a mutation tool with 10 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain what the tool returns (e.g., a run object or status), error conditions, or side effects, leaving significant gaps for an agent to use it correctly.

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 10 parameters. The description adds no additional meaning beyond mentioning 'optional parameters', which is redundant. Baseline 3 is appropriate as the schema handles parameter semantics adequately.

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

Purpose3/5

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

The description states the action ('Run a pipeline') and mentions optional parameters, but it's vague about what 'run' entails (e.g., triggering execution, creating a run record). It doesn't differentiate from sibling tools like 'execute_pipeline_job_run' or 'get_pipeline_run', leaving ambiguity in scope.

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?

No guidance is provided on when to use this tool versus alternatives like 'execute_pipeline_job_run' or 'create_pipeline_from_description'. The description lacks context about prerequisites, such as needing an existing pipeline, or exclusions, making it unclear in the broader toolset.

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