Tricentis qTest ACTION
List Defect Fields
List all available fields for defects in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before submitting or updating defects. Pass
fields (e.g. ["id", "label", "required"]) to keep only those attributes per field — some fields' allowed_values lists are long, so omitting them when you only need the field ID/label keeps the response small. Example: projectId: 1 → returns [{id: 1, label: "Summary", attribute_type: "String", required: true}, {id: 2, label: "Status", attribute_type: "String", allowed_values: [{label: "New", value: "1"}], required: true}]. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Tricentis qTest account once, then configure and run List Defect Fields 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-list-defect-fields",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
tricentis_qtest: { authProvisionId: "apn_xxxxxxx" },
projectId: "Project ID",
fields: ["Fields"],
},
})
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-list-defect-fields",
"configured_props": {
"tricentis_qtest": { "authProvisionId": "apn_xxxxxxx" },
"projectId": "Project ID",
"fields": ["Fields"]
}
}'// 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-list-defect-fields",
arguments: {
projectId: "Project ID",
fields: ["Fields"],
},
})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 |
fields Fields | string[] | Optional list of attribute names to include per field object (e.g. ["id", "label", "required"]) — omit to return every attribute, including allowed_values (today's default). 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-list-defect-fields
- Version
- 0.0.1
- App
- Tricentis qTest
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗