Skip to main content
Glama

查询 TAPD 迭代列表

tapd_list_iterations
Read-only

Retrieve a list of iterations from a TAPD project with filters by ID, name, status, and more. Use this to select the correct iteration for creating or updating requirements.

Instructions

查询 TAPD 项目迭代列表,支持按迭代 ID、名称、状态过滤,以及描述、起止时间、迭代类别、计划应用、创建人、创建/修改/完成时间、锁定人、自定义字段等,并可自定义排序(order)与翻页;用于创建或更新需求时选择 iteration_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo迭代 ID,TAPD 支持多 ID 查询
nameNo迭代名称,TAPD 支持模糊匹配
pageNo页码,默认 1
limitNo返回数量上限,默认 50,最大 200
orderNo可选,排序规则,格式「字段名 asc|desc」(如 created desc),不传默认 modified desc
lockerNo可选,锁定人 TAPD nick
statusNo迭代状态,系统状态为 open(开启)/done(已关闭),自定义状态可传中文名
createdNo可选,创建时间,TAPD 支持时间查询
creatorNo可选,创建人 TAPD nick
enddateNo可选,结束时间,TAPD 支持时间查询
modifiedNo可选,最后修改时间,TAPD 支持时间查询
completedNo可选,完成时间
startdateNo可选,开始时间,TAPD 支持时间查询
descriptionNo可选,详细描述
plan_app_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 自定义字段配置接口获取
workitem_type_idNo可选,迭代类别 ID
Behavior5/5

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

The readOnlyHint annotation is consistent with the query nature. The description provides extensive behavioral context: support for multiple IDs, fuzzy matching, time queries, sorting, pagination, and custom field filtering. No contradictions.

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 a single sentence that packs a lot of information. It is front-loaded with the main action. While slightly lengthy, it is efficient and each component adds value.

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

Completeness4/5

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

Given 18 parameters, 100% schema coverage, and no output schema, the description adequately covers the tool's purpose and usage. It does not detail return format, but that is acceptable for a list tool; the context is complete enough for an AI agent.

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 coverage is 100%, so the description does not need to explain schema fields. However, it adds value by summarizing the filtering capabilities and the use case (selecting iteration_id). This exceeds the baseline of 3.

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 the tool queries TAPD iteration lists with filtering, sorting, and pagination. It distinguishes from sibling tools like tapd_list_bugs and tapd_list_stories by focusing on iterations, and explicitly mentions its use for selecting iteration_id in create/update operations.

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?

The description hints at usage context (when creating/updating requirements) but does not explicitly say when not to use this tool or mention alternatives. The sibling list tools are distinct, so the usage is clear enough.

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