Skip to main content
Glama

创建 TAPD 需求

tapd_create_story

Create a confirmed TAPD requirement with assignee, priority, iteration, custom fields, and more. Requires explicit user confirmation before submission.

Instructions

在 TAPD 中创建一个已确认的新需求,支持设置处理人、优先级、迭代、父需求、标签、排期、工时、自定义字段等。创建前建议先用 tapd_search_users 确认处理人的 nick;不传处理人则默认指派给当前登录用户。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo可选,抄送人。与处理人同为 TAPD 用户 nick,参考 owner 格式,多个以分号分隔(如 a;b;)
dueNo可选,预计结束日期(YYYY-MM-DD)
nameYes需求名称
sizeNo可选,规模
typeNo可选,类型
beginNo可选,预计开始日期(YYYY-MM-DD)
labelNo可选,标签,不存在时自动创建,多个以英文竖线(|)分隔
effortNo可选,预估工时
exceedNo可选,超出工时
moduleNo可选,所属模块
ownersNo可选,需求处理人 TAPD nick 列表;建议先调用 tapd_search_users 确认
remainNo可选,剩余工时
sourceNo可选,来源
featureNo可选,特性
versionNo可选,版本
confirmedYes必须为 true,表示用户已明确确认创建该 TAPD 需求
developerNo可选,开发人员。与处理人同为 TAPD 用户 nick,参考 owner 格式,多个以分号分隔(如 a;b;)
parent_idNo可选,父需求 ID,用于创建子需求
tech_riskNo可选,技术风险
release_idNo可选,发布计划 ID
test_focusNo可选,测试重点
category_idNo可选,分类 ID
descriptionYes需求详细描述,支持 TAPD 富文本 HTML
iteration_idNo可选,迭代 ID
templated_idNo可选,模板 ID。从需求模板创建时使用
workspace_idYesTAPD 项目 ID(必填)。可先用 tapd_list_bugs / tapd_list_stories 跨项目查询,或 tapd_list_workspaces 获取目标项目 ID
custom_fieldsNo可选,自定义字段透传。key 为 TAPD 字段名(custom_field_*、cus_* 或 custom_plan_field_*),原样提交;具体字段名通过 TAPD 自定义字段配置接口获取
apply_templateNo可选,模板选项,多个以英文逗号分隔(如 preset_stories,preset_tasks,分别预设子需求/子任务),需配合 templated_id
business_valueNo可选,业务价值
priority_labelNo可选,优先级标识,推荐使用此字段以兼容自定义优先级(如 High/Medium/Low)
effort_completedNo可选,完成工时
workitem_type_idNo可选,需求类别 ID
is_apply_template_default_valueNo可选,是否从模板继承默认值/保密设置(仅 0/1,1 继承),需配合 templated_id
Behavior2/5

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

No annotations provided, so description must carry full burden. It discloses creation with confirmation requirement and default owner assignment, but does not describe return value, side effects, rate limits, or error handling. The lack of output schema amplifies this gap.

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?

Two sentences front-loaded with purpose and capabilities. The second sentence provides a crucial usage tip. Minimal waste, but the first sentence is long; could be slightly more structured.

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?

For a complex tool with 33 parameters and no output schema, the description is adequate but lacks explanation of return value, failure modes, and differentiation from sibling write tools. The prerequisite guidance is helpful but not comprehensive.

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 description coverage is 100% with detailed parameter docs. The description adds value by advising pre-use of tapd_search_users for owners, clarifying default owner behavior, and noting label auto-creation. This supplements the schema without redundancy.

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?

The description clearly states it creates a confirmed requirement in TAPD, listing key settable fields. It implicitly distinguishes from sibling tools like tapd_create_bug by specifying it is for stories/requirements.

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

Usage Guidelines4/5

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

Provides explicit guidance to first use tapd_search_users to confirm owner nick and notes default owner behavior. Lacks explicit when-not-to-use or comparison with update tools like tapd_writeback_story, but the advice is actionable.

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/sun-jingtao/tapd-mcp-server'

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