Skip to main content
Glama

调用任意 TAPD OpenAPI 接口

tapd_call_api

Execute arbitrary REST calls to TAPD OpenAPI for tasks, stories, modules, wiki, timesheets, and other resources not covered by dedicated tools.

Instructions

通用透传工具:直接调用 TAPD OpenAPI(https://api.tapd.cn)的任意 REST 接口,用于专用工具未覆盖的场景(任务、工时、测试计划、模块/版本配置、Wiki、看板等)。path 为官方文档(open.tapd.cn)中每个接口标注的 URL 路径,例如 GET /tasks(获取任务)、GET /stories/count(需求数量)、GET /modules(模块配置)、POST /timesheets(新增工时)。路径没有统一推导规则,不确定时应以官方文档为准,不要凭猜测拼路径——按 REST 直觉猜容易踩空,例如 Wiki 列表是 /wikis 而非 /wiki,/boards、/reports 也都不是有效路径。几乎所有接口都需要 workspace_id 参数。查询类接口默认返回 30 条,可用 page/limit 翻页。文件上传(multipart)不走本工具,请使用 tapd_upload_bug_attachment / tapd_upload_bug_image。注意:POST 写操作默认禁用,需在 MCP 配置 env 中设置 TAPD_ALLOW_RAW_WRITE=true,且每次调用需传 confirmed=true;优先使用专用写入工具(tapd_create_bug / tapd_writeback 等)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoPOST 请求体参数,仅 method=POST 时使用;默认按表单序列化,值为数组/对象时需配合 body_format: "json"
pathYesTAPD 接口路径(api.tapd.cn 之后的部分),如 /tasks、/stories/count、/timesheets/delete_timesheets
methodNoHTTP 方法,默认 GET;TAPD 查询用 GET,新增/修改/删除用 POST
paramsNoGET 查询参数,如 { workspace_id: "123", limit: 10 }
confirmedNomethod=POST 时必须为 true,表示用户已明确确认本次写操作;GET 无需传
body_formatNoPOST 请求体格式,默认 form(application/x-www-form-urlencoded);接口文档要求 JSON 请求体(如 batch_update_story 的 workitems 数组)时传 json
Behavior5/5

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

Discloses behavioral traits beyond the readOnlyHint annotation: it can perform writes but is controlled, requires path to match official docs, pagination defaults to 30, file uploads not supported, workspace_id required, POST body format options, and need for explicit confirmation. No contradiction with annotations.

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?

Long but dense with useful information. Front-loaded with purpose and examples. Each sentence adds value, though could be slightly trimmed. Structured logically from overview to details.

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?

Comprehensive given complexity: covers purpose, usage guidelines, all parameter semantics, behavioral traits (write control, path rules, pagination, file upload exclusion, workspace_id requirement), and alternative tools. No output schema but that's acceptable for a generic pass-through tool.

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

Parameters5/5

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

Schema has 100% coverage, but description adds significant meaning: provides path examples and pattern explanation, clarifies use of data vs params, explains when to use body_format json vs form, and notes that workspace_id is needed. Description complements schema well.

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?

Clearly states it's a universal pass-through tool to call any TAPD OpenAPI REST endpoint for scenarios not covered by dedicated tools. Provides verb (call/invoke) and resource (TAPD OpenAPI), and distinguishes from siblings by noting it's for uncovered scenarios.

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?

Explicitly states when to use (uncovered scenarios) and when not to use (prefer dedicated tools for file uploads and write operations). Gives context on POST write operation restrictions, requiring environment variable and confirmed=true, and advises to use dedicated write tools like tapd_create_bug.

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