Tricentis qTest ACTION
Update Requirement
Update ONE existing requirement in a qTest project. Use List Requirements to find the requirement ID and List Requirement Fields to discover field IDs for the Properties parameter. Name is required by the API on every update — resupply the requirement's current name (from Get Requirement) if you only want to change Properties. This tool has no bulk/mass-update mode — before calling it repeatedly to apply the same change across many requirements, confirm the full scope (which requirements, what change) with the user first; do not sweep an entire project's requirements on a single broad instruction. If you ask for that confirmation and don't receive an explicit yes, STOP — do not call this tool anyway. Proceeding without an actual confirmation is exactly the behavior this warning exists to prevent, even if the original instruction sounded broad enough to imply it. This warning is about scope (which/how many requirements), not about calling this tool at all — a single, already-specific instruction (a named requirement ID and field change) needs no extra confirmation. Example:
projectId: 1, requirementId: "101", name: "User can log in", properties: "[{\"field_id\": 3, \"field_value\": \"1\"}]" → returns the updated requirement object. See the documentation- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Tricentis qTest account once, then configure and run Update Requirement from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "tricentis_qtest-update-requirement",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
tricentis_qtest: { authProvisionId: "apn_xxxxxxx" },
projectId: "Project ID",
requirementId: "Requirement ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "tricentis_qtest-update-requirement",
"configured_props": {
"tricentis_qtest": { "authProvisionId": "apn_xxxxxxx" },
"projectId": "Project ID",
"requirementId": "Requirement ID"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "tricentis_qtest",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "tricentis_qtest-update-requirement",
arguments: {
projectId: "Project ID",
requirementId: "Requirement ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
projectId Project ID | string | The ID of a project, e.g. 1. Use the List Project ID Options action to retrieve available project IDs. Required |
requirementId Requirement ID | string | The ID of a requirement. Use the List Requirements action to retrieve available requirement IDs. Required |
name Name | string | Updated name for the requirement. Required by the API on every update — pass the current name unchanged if you only want to change Properties. Required |
properties Properties | string | A JSON array of field properties to set on the record. Use List Requirement Fields to discover requirement field IDs, or List Defect Fields to discover defect field IDs. Example: [{"field_id": 3, "field_value": "1"}] Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- tricentis_qtest-update-requirement
- Version
- 1.0.0
- App
- Tricentis qTest
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗