Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

create_work_item

Create work items to organize tasks in Alibaba Cloud DevOps projects. Define subject, type, assignee, and custom fields for tracking.

Instructions

[Project Management] Create a work item. 描述字段使用提示:

  • description 支持 Markdown / 富文本,需配合 formatType("MARKDOWN" 或 "RICHTEXT")。

  • 描述中插入图片三步法:① 先建工作项(本工具, description 可先为空或占位);② 调 create_workitem_attachment 上传图片拿到返回值中的 embedMarkdown 或 embedHtml;③ 调 update_work_item 把拼好的 description 写回。✅ 报错点:不要使用 create_workitem_attachment 返回的 url 字段,那是 30 秒过期的 OSS 临时签名。

  • 实际工时(fieldId 101587)与预计工时(fieldId 101586)为云效受控系统字段,不能通过本工具的 customFieldValues 修改;请改用 create_effort_record / create_estimated_effort

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
spaceIdYesSpace ID, project unique identifier
subjectYesWork item title
workitemTypeIdYesWork item type ID
assignedToYesAssignee user ID
customFieldValuesNoCustom field values
descriptionNoWork item description
formatTypeNoDescription format type. RICHTEXT (rich text, default) or MARKDOWN (markdown format). Use MARKDOWN when description contains markdown syntax
labelsNoAssociated label IDs
parentIdNoParent work item ID
participantsNoParticipant user IDs
sprintNoAssociated sprint ID
trackersNoCC user IDs
verifierNoVerifier user ID
versionsNoAssociated version IDs
Behavior5/5

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

With no annotations, description fully discloses behaviors: description supports Markdown/richtext with formatType, explains OSS URL expiry (30 seconds), and clarifies limitations on custom field edits.

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?

Description is lengthy but well-structured with bullet points and step-by-step guidance. Every sentence adds value, though could be slightly more concise.

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

Completeness5/5

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

Given complexity (15 parameters, no output schema), description thoroughly covers critical workflows, pitfalls, and alternative tools, ensuring correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 15 parameters (100% coverage). Description adds value by explaining description format handling and forbidden fields, exceeding baseline expectations.

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

Purpose5/5

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

Description clearly states 'Create a work item' in project management context. It distinguishes from sibling tools like create_workitem_attachment, create_effort_record, etc., by specifying its role in creating the initial work item.

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use guidance. Details image upload workflow with steps and warns against using customFieldValues for effort fields, directing to dedicated tools (create_effort_record, create_estimated_effort).

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